list_inventory_tiers

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses the HTTP method and path, Bearer-token authentication requirements, and specific 403/404 error semantics. It does not cover pagination or rate limits, but the auth and error details are substantial transparency beyond the schema.

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 front-loaded with the core purpose and uses clear sections for endpoint, filters, errors, and authentication. Every line is relevant, and no sentence is wasted or redundant without purpose.

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 list tool with no annotations and no output schema, the description covers important invocation context: auth, endpoint, filters, and error behavior. It still omits return-shape and pagination details, but it is largely complete for selecting and correctly calling the tool.

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 100%, so the schema already documents all three parameters. The description repeats the filter meanings ('Filter by tier group', 'Filter by whether tier counts toward capacity') but adds no syntax, format, or usage detail beyond the schema.

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 gives a specific verb and resource: 'List Inventory Tiers for an Event.' It also states the exact endpoint, making the tool's scope unambiguous. This clearly distinguishes it from sibling tools like get_inventory_tier, create_inventory_tier, and update_inventory_tier.

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 implies usage by naming the required event context and available filters, but it does not explicitly say when to use this tool versus get_inventory_tier or other inventory-tier siblings. There are no exclusions or alternative-tool routing instructions, so the agent must infer proper usage.

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