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

Annotations already declare the operation as read-only and idempotent, so the description does not need to repeat that. It adds context about the specific content returned (price, sale status, URL, events), but does not disclose any additional behavioral aspects such as caching or data freshness.

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 a single sentence, front-loaded with the verb, and contains no extraneous information. Every word contributes meaning, making it appropriately sized and well-structured.

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?

With no output schema, the description serves as the sole specification of return content, listing all expected data points (pass, price, sale status, URL, events). This is complete for a simple read-only tool with no parameters.

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?

The tool has zero parameters, so the schema trivially covers everything. The description clarifies the concept of 'pase vigente' (current pass) as the implicit context, but no parameter semantics are needed. Baseline 4 applies.

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 uses the specific verb 'Devuelve' (returns) and clearly identifies the resource as 'el pase vigente' (the current pass), along with its price, sale status, official URL, and included events. This distinguishes it from sibling tools focused on events, companies, or general information.

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 when the agent needs information about the current pass, but it does not explicitly state when to use this tool versus alternatives or mention any exclusions. Since there are no parameters or preconditions, guidance is limited to interpreting the tool's purpose.

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