infoset_search_tickets

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only repeats the fact that it searches by keyword, with no information about matching logic, return format, pagination behavior, read-only nature, or any side effects. This goes beyond what the name already implies, providing minimal additional transparency.

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, front-loaded sentence, 'Search Infoset tickets by keyword and optional filters', that is concise and free of fluff. Every word adds value, and it is appropriately sized for the tool's simplicity.

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?

Given that there is no output schema and no annotations, the description is insufficient for a 5-parameter tool. It does not explain what the search returns, how results are matched, or any pagination behavior, leaving significant gaps for the agent to infer. The schema covers parameters, but the description lacks broader context.

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 all parameters are already documented in the input schema. The description's mention of 'keyword and optional filters' summarizes the schema but adds no new meaning beyond what the schema provides, warranting the baseline score of 3.

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's function: 'Search Infoset tickets by keyword and optional filters'. It uses a specific verb ('Search') and resource ('Infoset tickets'), and the scope ('by keyword') distinguishes it from sibling tools like list_tickets and get_ticket, which likely have different purposes.

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 usage is implied by the word 'Search' and the optional filters, suggesting this tool is for targeted keyword-based queries rather than simple listing. However, it does not explicitly mention when to use it over alternatives or when not to use it, so only implied guidance is provided.

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