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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe-read nature is covered. The description adds behavioral details about filtering and pagination, but omits response format, pagination mechanics, and date format expectations, offering only modest clarity beyond the 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 exactly two sentences, front-loaded with the core purpose, and contains no filler or redundant details. Every element adds value.

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 no output schema and 0% parameter coverage, placing a heavy burden on the description. It adequately communicates the tool's core listing and filtering capabilities, but lacks parameter semantics, pagination details, and return shape, making it minimally complete for an agent to invoke correctly.

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, but it only mentions filtering by status/date range and pagination in the abstract. It fails to explain the account parameter, offset/page_size semantics, or start_date/end_date format, leaving most of the 6 parameters underdocumented.

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 identifies the operation (List Orders) and the resource (Productions orders in the workspace), using a specific verb and noun combination. It distinguishes itself from sibling elevenlabs_public_get_order by explicitly indicating the plural list context and 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 useful context by stating it lists orders in the workspace and supports filtering/pagination, which implies when to use it. However, it does not explicitly mention alternatives like elevenlabs_public_get_order or provide when-not-to-use guidance, so it only implies usage rather than stating it.

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