send_document

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

With no annotations, the description carries full burden. It mentions that document can be a URL, file path, or file_id, and notes caption character limit and parse_mode reference. However, it does not disclose destructive hints, authentication needs, rate limits, file size constraints, or behavior on failure. Critical gaps remain for a mutation tool.

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 well-structured with a one-line summary followed by a bulleted Args list. It is concise and front-loaded. Minor improvement could be reducing redundancy in parameter names, but it is clear and 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?

Given the tool complexity (5 params, required document) and presence of an output schema, the description covers parameter semantics well but lacks usage guidelines and behavioral transparency. It references send_message for parse_mode but does not provide independent context. Overall adequate but with noticeable gaps.

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 fully compensates. Each parameter is explained: document (URL, path, file_id), chat_id (default chat), caption (max 1024), parse_mode (see send_message), disable_notification (silent). This adds essential meaning beyond the schema's type-only definitions.

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 action: 'Send a file/document to a Telegram chat.' This is a specific verb+resource combination. The title and sibling tools (send_message, send_photo) indicate distinct purposes, so the tool is well-differentiated.

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 explicit guidance on when to use this tool versus alternatives like send_message or send_photo. The description only explains parameters, not the context for choosing this tool. Usage is implied by the purpose, but no when-not or exclusion criteria are given.

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