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

Annotations include readOnlyHint=false, destructiveHint=false, so they don't fully cover safety profile. Description adds that multiple items are zipped, which is helpful behavior. However, it doesn't disclose other behaviors like output format handling or potential limits, but no contradiction with annotations.

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?

Three sentences, front-loaded with purpose, and each sentence adds value: first states action, second and third explain behavior based on input. No wasted 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?

For a download tool with no output schema and 0% schema coverage, the description covers the main behavior but omits details about output format parameter, account parameter, and potential errors or size limits. However, the tool is relatively simple and the core behavior is well explained.

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 description coverage is 0%, so description must compensate. The description explains 'history_item_ids' semantics (single vs. multiple => audio vs. zip). However, 'output_format' and 'account' parameters are not explained beyond schema type definitions. The description adds meaning for the primary parameter but leaves the other two undocumented.

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?

Description clearly states verb ('Download') and resource ('History Items'), and distinguishes between single vs. multiple items behavior. It is specific enough to differentiate from sibling tools like delete_speech_history_item or get_audio_full_from_speech_history_item.

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 implies when to use (when needing to download history items) and distinguishes between single vs. multiple item behavior. It doesn't explicitly mention alternatives or when not to use, but the distinction between single and multiple IDs provides useful context.

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