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

Annotation contradiction: readOnlyHint is false, but description explicitly says 'Retrieves a history item' and uses 'Get'. This suggests a write or mutating operation per annotation, conflicting with the read-only nature described. No clarification of side effects or why it is not read-only.

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 very short (two sentences), which is concise, but it lacks necessary detail. It is not front-loaded with critical info beyond the name; the first sentence just restates the tool name.

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?

No mention of return value, error conditions, authentication, or relationship to other history tools. The annotation contradiction further reduces completeness, leaving the agent confused about side effects.

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?

Description adds context for history_item_ids (batch) but does not explain 'account' parameter or clarify the distinction between history_item_id and history_item_ids beyond batch. With 0% schema coverage, more parameter guidance is needed.

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 'Retrieves a history item' and the tool name explicitly includes 'get_speech_history_item', so the purpose is evident. However, it does not differentiate from sibling tools like 'elevenlabs_get_speech_history' or 'elevenlabs_download_speech_history_items', missing a chance to clarify 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?

Only notes 'Bulk support: accepts history_item_ids for batched execution', which is a capability, not usage guidance. No mention of when to choose this over alternatives like listing history or downloading items, nor context like prerequisites or authentication.

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