send_voice

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

Discloses auto-conversion to SILK, same rate limiting, and no reply_to parameter. Annotations confirm mutation (readOnlyHint=false). Adds valuable context beyond annotations, though could mention size limits or error cases.

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?

Front-loaded with main purpose, followed by conversion info and sibling comparisons. Three sentences plus a behavior note are concise and well-structured. Could be slightly more streamlined, but effective.

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?

Covers purpose, usage alternatives, conversion, and behavioral constraints. No output schema needed; complexity moderate. Missing explicit parameter details but otherwise complete for sending a voice message.

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 coverage is 0%. Description does not explicitly map parameters to variables. While overall context hints at target and audio, it lacks detailed semantics for each parameter, which is needed given no schema descriptions.

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?

Clear verb 'Send' with specific resource 'base64-encoded voice message to a QQ group or friend.' Differentiates from siblings like send_message, send_image, send_file by naming alternatives.

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?

Explicitly states when to use this tool vs alternatives ('For text use send_message...'). Also mentions rate limiting same as send_message and notes that voice messages cannot be replied to.

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