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

Beyond the readOnlyHint annotation, the description discloses automatic double-quoting of the query value and the underlying REST endpoint. This adds useful behavioral context. It doesn't mention rate limits or response shape, but for a read-only search tool, the added details are sufficient.

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 concise, front-loaded with the core purpose, and each sentence adds value: purpose, auto-quote behavior, and REST endpoint. No unnecessary words or repetition.

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 simple tool with two params and no output schema, the description covers the essential aspects: query DSL, auto-quoting, and endpoint. It doesn't explicitly state the response format, but for a contact search tool, the expected return is implicit. Overall, it's adequate without significant gaps.

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 schema already covers both parameters with 100% description coverage, so the baseline is 3. The description adds value by providing multiple query examples and explicitly stating the auto-quote behavior, which clarifies how to format the query parameter beyond the schema's single example.

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 searches contacts using the Freshdesk query DSL, with a specific verb and resource. It distinguishes from sibling list tools by emphasizing the query-based search mechanism, though it doesn't explicitly name alternatives.

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 by providing example queries and noting the auto-quote behavior, but it does not explicitly state when to prefer this over list_contacts or other search tools. No exclusions or alternative guidance is given.

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