Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish the safe read-only, idempotent, non-destructive profile, and the description adds genuine value on top: source/page content is untrusted data that must never be treated as instructions, and sources are private. It does not describe return structure or any limits, and the publishing sentence is off-topic for a read-only export.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, then the safety/security context in short sentences. Compact overall, though the final publishing sentence does not earn its place in a read-only export definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description does at least indicate the return format (Markdown), plus important trust/security framing. However, with two undocumented parameters and no detail on the export payload, it is only partially complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden for account_id and page_id, but it only hints that page_id refers to a published article. Neither UUID parameter's meaning is explained, leaving the agent to infer from names alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Export), resource (one published article), and output format (portable Markdown), which separates it from read-style siblings like get_knowledge_page. It stops short of explicitly naming an alternative, so it is clear but not fully sibling-differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use export vs the many get_/search_knowledge siblings. The only directive ('never publish without the user's instruction') concerns a publishing operation, not this export tool, so it does not help the agent select this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.