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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description doesn't need to restate those. It adds useful behavioral context by noting that Music and SFX generations cannot be retrieved via the API and that bulk support is available for certain parameters. However, it does not mention pagination, sorting, or output structure, which could be relevant. The added context is moderate given the existing 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?

The description is concise, with a clear first sentence that states the primary purpose. The second sentence provides an important exclusion note, and the third sentence adds bulk support information. It is front-loaded with the core purpose and avoids unnecessary verbiage, making it efficient and well-structured.

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?

The tool has 13 optional parameters, no output schema, and no description of return values or pagination. The description only covers the list scope and a vague note about bulk support. It fails to explain filtering options (date, source, model, etc.), sorting, or how to handle large result sets. Given the complexity and lack of schema coverage, the description is far from complete.

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 the description must compensate for explaining parameters. It only mentions three parameters (start_after_history_item_ids, voice_ids, model_ids) in the context of 'batch execution,' without detailing their individual purposes. The other 10 parameters (search, source, account, page_size, etc.) are entirely unexplained, leaving the agent to infer their meanings from names alone. This is insufficient for a tool with 13 optional parameters.

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's purpose: 'List Generated Items' and specifies the scope (TTS, STS, Studio, dubbing) while explicitly excluding Music and SFX. This differentiates it from related tools like get_speech_history_item_by_id and delete_speech_history_item by indicating it's a listing operation with a defined 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?

The description provides context about what the tool does (lists generated items) and notes bulk support, but it does not explicitly mention when to use this versus alternatives like getting a single item or downloading. The exclusion of Music/SFX is a limitation, but there's no clear guidance on when to prefer this tool over siblings. The usage context is implied but not explicit.

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