Voice messages

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description's mention of 'Read-only' adds little. It adds value by noting the temporary nature of download URLs, but omits details like authentication needs or rate limits.

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 short sentences with zero wasted words. It front-loads the core function and provides critical usage hints efficiently.

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 simple retrieval tool with rich annotations and full parameter coverage, the description covers purpose, source of IDs, and temporary nature. It could be more complete by noting the output structure (e.g., 'returns an object with temporary URLs'), but overall it's sufficient.

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 input schema covers both parameters with descriptions (100% coverage). The tool description adds meaningful context: voice_ids are sourced from messenger_get_messages_v3, and user_id defaults to Profile_id from .env, enhancing the schema's information.

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 tool 'Returns temporary download URLs for voice messages by their voice_id', specifying the verb, resource, and scope. It differentiates from sibling messenger tools by focusing on voice files and referencing the source of voice_id from messenger_get_messages_v3.

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 provides clear context by linking voice_ids to messenger_get_messages_v3, implying a sequential usage pattern. It also advises immediate download due to temporary links, but does not explicitly exclude other uses or name alternative tools.

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