search_tickets

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

With no annotations, the description carries full responsibility for behavioral disclosure. It mentions key behaviors: query length limit, 300-result cap, and exclusion of archived tickets. It does not detail pagination, return format, or authentication, but for a read-only search tool these are less critical. 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 extremely concise, using two short sentences to convey the tool's purpose, query syntax, limits, and archived-ticket exclusion. No unnecessary words or fluff.

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 the tool's simplicity (one parameter, no output schema), the description covers the essential aspects: what it does, how to use it, and key constraints. It doesn't explicitly state return type or pagination, but these are minor omissions for a search tool of this complexity.

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%—the single query parameter is described with its max length in both the schema and the tool description. The description adds little beyond what the schema already provides, only redundantly stating the Freshdesk query syntax and max length.

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 uses a specific verb ('Search') and resource ('tickets'), and specifies the mechanism ('Freshdesk query syntax'). This distinguishes it from siblings like list_tickets (which likely lists all tickets) and get_ticket (which fetches a single ticket).

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 provides clear context for when to use the tool: when a search query is needed, with explicit constraints like max length and result limit. However, it does not explicitly name alternatives or state when not to use it, leaving some usage guidance implicit.

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