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

Annotations already declare destructiveHint=true, so mutation is clear. Description adds context about file size (50MB) and format support, but doesn't discuss rate limits, permissions, or error behavior. With annotations present, this is adequate but not exceptional.

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-sentence description is efficient and front-loaded: first sentence states action and key constraints, second sentence suggests use cases. No fluff, well-structured for quick comprehension.

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?

Tool has output schema, so return details not needed. Description covers purpose, file types, size, and use cases. Could mention that document URL must be publicly accessible or require bot permissions, but completeness is satisfactory for a simple send tool.

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 has 100% coverage, each parameter with a description. The description adds the 50MB limit (not in schema) but little else for individual parameters. Baseline 3 is appropriate as schema does the heavy lifting.

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?

Clearly states 'Send a file/document to a Telegram chat' with specific format examples (PDF, CSV, ZIP) and a size limit. Distinguishes from sibling tools like send_message and send_photo by focusing on document sending.

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?

Mentions use cases like 'sending reports, data exports, generated files' but lacks explicit when-not-to-use or comparison to other send tools. However, the context of sibling tools and the specific verb 'send_document' imply its domain.

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