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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds only the bulk support note. It doesn't explain what a 'snapshot' is, whether it returns content-only metadata, how snapshots differ from current chapter state, or whether results are cached. For a read operation with readOnly=true annotation, the description should clarify what the snapshot represents and any caveats (e.g., whether it reflects saved state 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. The first sentence is somewhat tautological ('Get Chapter Snapshot. Returns the chapter snapshot.'), but the bulk support note adds useful information. It's concise and front-loaded, though the tautological repetition wastes a bit of space.

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 tool with 7 parameters, 3 required, and 0% schema coverage, the description is severely incomplete. It doesn't explain what a chapter snapshot is, how it differs from a chapter, when snapshots are created, or whether the bulk parameters replace or supplement the singular ones. The relationship between required singular parameters and optional plural parameters is unclear. With no output schema and no transaction details, this falls short of being fully usable by an agent.

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 description provides no parameter-level details beyond the schema. The input schema has 7 parameters with 0% description coverage (schemas themselves have no descriptions). The description only mentions the bulk parameters (project_ids, chapter_ids, chapter_snapshot_ids) without explaining their relationship to the singular required ones. It doesn't clarify whether the singular required parameters are alternatives to the plural bulk parameters, or whether both must be provided together. This is confusing.

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 states 'Get Chapter Snapshot. Returns the chapter snapshot.' This clearly identifies the action (get) and resource (chapter snapshot), but it doesn't distinguish this from the similarly named sibling tool `elevenlabs_get_chapter_snapshot_endpoint` (which appears to be the same name) or `elevenlabs_get_chapter_snapshots`. The purpose is clear but lacks differentiation.

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 mentions 'Bulk support: accepts project_ids, chapter_ids, chapter_snapshot_ids for batched execution.' This provides some guidance on when to use the plural parameters, but it doesn't explain when to use this tool versus other snapshot-related tools like `elevenlabs_get_project_snapshot_endpoint` or `elevenlabs_get_chapter_by_id_endpoint`. No exclusions or alternatives are mentioned.

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