Voice messages

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

The description adds the behavioral detail that links are temporary, which is beyond the readOnlyHint annotation. It confirms the read-only nature, but does not disclose additional side effects or the underlying mechanism.

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 three sentences, front-loaded with the core purpose, and includes essential context about input source and link temporariness. No extraneous words.

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 simple nature of the tool and good annotations, the description covers key aspects: what it returns, input source, and a warning. Missing details about the output structure (e.g., whether it returns an array or object), but without an output schema, some gap is acceptable.

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 100%, so the baseline is 3. The description adds context about how to obtain voice_id values (from messenger_get_messages_v3), which is helpful, but adds little beyond what the schema already describes for user_id.

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 it returns temporary download URLs for voice messages, specifying the resource (voice messages) and action (returns URLs). It distinguishes from siblings in the messenger group by focusing on voice file retrieval.

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 explains that voice_id values come from messenger_get_messages_v3, providing clear source of input. It also notes the temporary nature of links. However, it does not explicitly mention when not to use this tool or list alternatives, though the sibling context implies the appropriate usage.

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