List Alternative Response Sets

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

Annotations already indicate read-only, idempotent, and non-destructive. Description adds pagination details and return type (though incorrectly mentions Inspections). Adds value beyond annotations but includes an error.

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?

Description is four sentences, includes endpoint info, and is reasonably compact. Could be slightly tighter but not overly verbose.

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 description fails to correctly state what is returned (alternative response sets) and misstates it as Inspections. Given no output schema, this is a critical omission. Pagination metadata is mentioned, but the core return type is wrong.

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 coverage is 100% with parameter descriptions. Description restates company_id as required and mentions page/per_page for pagination, adding minimal extra value.

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 the tool lists Alternative Response Sets, but then confusingly says to 'enumerate Inspections'. This inconsistency undermines clarity. The title properly indicates listing, so the purpose is discernible but muddled.

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?

Provides some usage context (paginated overview, find IDs, filter by query), but does not differentiate from siblings like 'show_alternative_response_set' or 'list_item_response_sets'. No explicit when-not or alternatives.

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