Send a file

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

The description only states that it sends a file, providing no additional context about side effects, error conditions, or file handling. The annotations (readOnlyHint=false) already signal a write operation, so the description adds no extra behavioral information.

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 front-loads the action and object. It is efficient and free of unnecessary details.

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?

The description covers the core intent and mentions the optional caption. It lacks explicit differentiation from the sibling 'send' tool, but for a simple file-sending operation, it provides sufficient context for an agent to understand the action.

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?

The description repeats the parameter explanations from the schema verbatim. Since the schema covers all parameters at 100%, the description adds no new meaning beyond what the schema already provides, resulting in a baseline score.

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 'Send' and the resource 'a local file to a chat', distinguishing it from the sibling 'send' tool which likely sends text messages. The scope is unambiguous.

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 does not explicitly indicate when to use this tool versus the sibling 'send' tool, nor does it mention any conditions or exclusions. The distinction is only implied by the name and the word 'file'.

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