Get Document (Outline)

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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, and no destructiveness. The description adds behavioral detail about the asMarkdown parameter returning full Markdown body, which is beyond annotations. It does not contradict annotations.

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?

Two concise sentences with no extraneous information. The key behavior and parameter are front-loaded, making it efficient.

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?

The description explains the asMarkdown behavior and the identifier methods, but does not describe the default return format (without asMarkdown) or error cases. Given no output schema, this is a minor gap; annotations provide safety context.

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 covers two parameters with id having a description but asMarkdown lacking one. The description compensates by explaining asMarkdown=true returns full Markdown body, adding value to the semantics.

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?

The description clearly states the tool fetches a document by id or slug, using a specific verb 'Fetch' and resource 'document'. This distinguishes it from sibling tools like outline_list_documents or outline_search.

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?

The description implies usage by identifying the primary identifier (id or slug) and a key flag (asMarkdown), but does not explicitly state when to choose this over alternatives like outline_get_collection or outline_search. However, the purpose is straightforward and self-explanatory.

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