get_audio_isolation_history

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe, idempotent read operation. The description adds no behavioral context beyond the name, such as pagination behavior or return format, but with annotations covering the safety profile, a baseline 3 is appropriate.

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 a single, efficient phrase that directly states the tool's function. It is appropriately sized and front-loaded, but it lacks structure beyond the title-like statement.

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 list tool that is read-only and idempotent, the description is minimally adequate. However, without an output schema, it should ideally explain what the history items contain or how pagination works, which it omits. It is complete enough to call the tool but not to fully understand its output.

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 has 100% description coverage, fully documenting the optional 'page', 'search', and 'page_size' parameters. The description adds no additional parameter meaning, but since the schema is self-sufficient and the description does not need to compensate, the baseline 4 for 0 required parameters with complete schema documentation is warranted.

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 names a specific verb (get) and resource (audio isolation history), making the tool's purpose clear. It is significantly better than its tautological title since it names the actual resource. However, it does not differentiate this list tool from the sibling 'delete_audio_isolation_history_item' or other history-related tools, leaving some ambiguity about 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 offers no explicit guidance on when to use this tool versus alternatives like 'get_speech_history' or 'get_audio_isolation_history_item'. It provides no context about prerequisites, what happens if there is no history, or how to retrieve a specific item instead of the list.

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