list_tickets

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

Although no annotations are provided, the description reveals a key behavioral trait: automatic filtering to the last 90 days. This adds value beyond the schema, though it omits other details like pagination or read-only nature.

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?

Two sentences, front-loaded with the main action, and no unnecessary words. The alternative is efficiently presented in the second sentence.

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 tool with 6 OData parameters and no output schema, the description is minimal. It covers the time scope but lacks details about return format or that it uses OData, though parameter descriptions fill some gap.

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% with each parameter having its own description. The tool description does not add parameter-specific meaning beyond the schema, so a baseline of 3 is appropriate.

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 verb 'Lista' and resource 'tickets', and specifies the scope 'atualizados nos últimos 90 dias', which distinguishes it from the sibling tool list_tickets_past.

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?

Explicitly states when not to use this tool ('Para tickets mais antigos') and directs to the appropriate alternative (list_tickets_past), providing clear usage guidance.

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