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

Adds significant behavioral details beyond annotations: it skips free, guest-list, and cancelled tickets, and returns results newest first. Annotations already indicate read-only, idempotent, non-destructive; description enhances with filtering and ordering behavior.

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?

Three efficient sentences, front-loaded with key details. No redundant or extraneous information. Every sentence earns its place.

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?

Covers input, filtering, ordering, and authorization. With no output schema, it describes returned fields. Lacks mention of pagination, rate limits, or error handling, which is acceptable for a simple list tool. Sufficient for an agent to use 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?

Only one parameter (event_id) with 0% schema description coverage. Description mentions 'Requires event_id' and context makes its purpose clear (identify the event). While it doesn't elaborate on format or constraints, the single parameter is adequately explained given the low complexity.

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?

Clearly states it lists paid ticket sales for a live event, specifying exact fields (buyer name/email, tier, amount, discount, promo code, date) and ordering (newest first). Distinguishes from siblings like list_guests by focusing on paid sales and explicitly skipping free/guest-list and cancelled tickets.

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 context: requires event_id and host status. However, no explicit guidance on when to use this vs. other list tools (e.g., list_guests for all guests) or when not to use it. The description implies its use case but lacks direct comparison to alternatives.

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