get_document

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions returning markdown text but does not specify whether the operation is read-only, idempotent, or has side effects. It also omits authentication or rate limit details.

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?

The description is a single, concise sentence that is mostly clear. However, the phrase 'by UUID, urlId, or share id' could be misinterpreted as three separate parameters, slightly reducing precision.

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?

Given the absence of an output schema and annotations, the description should provide more detail about the return structure and error scenarios. It only mentions markdown text, leaving other fields and potential issues unclear.

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 coverage is 0%, and the description introduces confusion by mentioning 'urlId' as a parameter, but the schema only includes 'id' and 'share_id'. The description does not clarify the meaning of 'id' (e.g., UUID or urlId) or how 'share_id' relates to the three mentioned identifiers.

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 verb 'Fetch', the resource 'single document', and specifies that it includes markdown text. It also lists three identifiers (UUID, urlId, share id), which differentiates it from sibling tools like 'list_documents' and 'search_documents'.

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 when you have a specific identifier, but it does not explicitly state when to use this tool versus alternatives like 'list_documents' or 'search_documents'. No exclusion criteria or prerequisites are mentioned.

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