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

Beyond the readOnlyHint annotation, the description reveals that query values are automatically wrapped in double quotes and provides example syntax. It does not mention return format or rate limits, but the auto-quote behavior is a valuable addition.

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?

Description is concise and front-loaded with the core purpose, followed by a behavioral note, useful examples, and REST endpoint. No wasted sentences.

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 two-parameter search tool, the description explains the DSL, quoting, and provides examples, which is sufficient. It does not describe the return payload, but with the tool being a search this is not critical; schema covers pagination.

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 already covers both parameters with descriptions, giving a baseline of 3. The description adds concrete query examples and the auto-wrap note, which helps the agent format queries correctly beyond the schema.

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?

Clearly states the tool searches tickets using Freshdesk's query DSL, with a specific verb and resource. The examples and REST endpoint further clarify its function and distinguish it from sibling tools like list_tickets and get_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 implies use for complex ticket searches via the DSL, but does not explicitly state when to prefer this over list_tickets or get_ticket. The examples illustrate capability, but no alternatives or exclusions are named.

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