buy-ticket

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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating no side effects. The description adds that the tool returns an order summary with price, date, venue, and purchase URL, confirming its read-only nature. No contradiction with 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 two sentences, front-loading the purpose and then a critical usage instruction. There is no superfluous content. The 'IMPORTANT:' emphasis is helpful but slightly redundant.

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 simple one-parameter tool with no output schema, the description adequately covers what the tool does, the prerequisite (ask for quantity), and the return value (order summary with purchase URL). It could mention that no actual purchase occurs, but the readOnlyHint implies that.

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 a description for 'quantity' (Number of people attending). The description adds behavioral guidance on how to obtain the quantity from the user, surpassing the schema's meaning.

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 states the tool gets a direct purchase link for ELC Conference 2026 tickets, distinguishing it from siblings like get-available-tickets or find-best-conference. The verb 'Get' and resource 'purchase link' are specific and unambiguous.

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 explicitly instructs the agent to ask the user for the number of people before calling, and to use that as 'quantity'. This is a clear usage guideline. However, it does not explicitly mention when not to use the tool or suggest alternatives, but the sibling list provides context.

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