send_file

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

No annotations are provided, so the description bears full responsibility for disclosing side effects, permissions, or expected outcomes. 'Send a File' reveals nothing about whether the operation mutates data, requires authentication, or has limitations. The agent is left blind.

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 two-word phrase, which is not conciseness but under-specification. It lacks any structure or highlighted critical information, failing to earn its place as a useful guide.

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 complexity (9 parameters, no annotations, no output schema), the description is critically insufficient. It does not explain what a file is, how it is sent, what the response contains, or how to select between the many send_* alternatives.

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?

With 9 parameters and 0% schema description coverage, the description adds no meaning to the parameter names. The ambiguity between body, mediaId, filename, and mediaType is entirely unresolved, and the agent receives no guidance on which fields are required or how they relate.

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 'Send a File' is a direct restatement of the tool name, providing a clear verb and resource but no differentiation from sibling tools like send_message, send_contact, or send_button. It does not specify what kind of file, the transport mechanism, or any unique scope.

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 send_file instead of other send_* tools, nor any context about prerequisites or exclusions. The description is entirely silent on usage scenarios.

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