send_file

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

With no annotations, the description carries the full burden and does add one meaningful behavioral detail: 'Requires confirm=true.' It does not disclose side effects, failure behavior, or whether the action is reversible, but the confirmation requirement provides useful operational context.

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 two short sentences with no filler. The core action is front-loaded, and the critical confirmation requirement is stated immediately. Every word earns its place.

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 tool with no annotations, no output schema, and zero parameter documentation in the schema, the description is too thin. It omits how to identify the recipient ('to'), what caption constraints are, and what happens when confirm is false. A simple tool still needs more operational detail.

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 must compensate. It adds meaning for filePath ('local file') and confirm ('requires confirm=true'), but leaves 'to' and 'caption' entirely unexplained. The agent still lacks enough information to fill these parameters correctly.

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 a specific verb ('send'), a resource ('local file'), and the supported content categories ('image/video/audio/document'). It is distinguishable from send_message by focusing on file transmission, though it does not explicitly name a sibling alternative.

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 gives clear context: use this tool to send a local file rather than a text message. However, it does not explicitly state when to choose this over send_message or post_status, nor does it mention any exclusions or prerequisites beyond the confirmation flag.

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