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

Annotations already mark the operation readOnly, idempotent, and non-destructive, and the description adds 'Returns a list of chapter IDs' and the bulk behavior rather than repeating those flags. It does not contradict the annotations and provides useful output and batching context beyond the structured metadata.

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 two front-loaded sentences: a clear purpose line and a compact bulk-support note. Every word contributes; there is no repetition or filler.

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 read tool with no output schema, the description states the return type (list of chapter IDs) and batching, but it leaves the relationship between required project_id and optional project_ids unclear and does not describe account. Given the low parameter explanation and absent output schema, the description is functional but not fully 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 carry parameter meaning, but it only explains project_ids as batch support. The required project_id and the account parameter receive no semantic detail beyond their names and types, leaving significant coverage gaps for a 3-parameter tool.

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 opens with 'Get Project Muted Tracks' and specifies 'Returns a list of chapter IDs that have muted tracks in a project,' giving a concrete verb, resource, and output. This clearly distinguishes it from sibling project/chapter getters like elevenlabs_get_project_by_id or elevenlabs_get_chapters.

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 only usage guidance is 'Bulk support: accepts project_ids for batched execution,' which indicates a batching option but does not say when to prefer this tool over other project or chapter read tools. No explicit alternatives or exclusions are stated, so usage remains mostly implied by the name and description.

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