send_document

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

No annotations are provided, so the description must disclose behavior, but it only mentions the source-directory restriction. It does not clarify how the target chat is chosen, what happens when chat_id is omitted, whether captions accompany the document, or what permissions are required. The output schema covers return values, but the operational behavior is still thinly described.

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 definition is a single front-loaded sentence with no wasted words. The key constraint follows immediately after the action. It is appropriately sized for the amount of information it chooses to convey, even though it omits necessary detail elsewhere.

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?

For a send operation with no annotations and three parameters, the description is too sparse. It omits chat targeting, caption behavior, file-type or size expectations, and any error conditions around disallowed directories. The output schema reduces the need to explain returns, but the call semantics remain incomplete.

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 needs to compensate for three undocumented parameters. It only indirectly clarifies that path must point inside an allowed directory. It says nothing about chat_id or caption, leaving most parameter meaning unexplained.

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 names a specific verb and resource: sending a file as a document. It adds the useful constraint that the file must come from an allowed directory. It does not explicitly distinguish itself from send_photo or explain chat targeting, so it stops short of a 5.

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 this tool instead of send_photo or send_message. It also does not explain when not to use it, such as for images that should be sent as photos. The allowed-directory phrase implies a precondition but is not framed as usage guidance.

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