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

readOnlyHint=true already establishes the safety profile, and the description adds a genuinely non-obvious behavioral trait: the query VALUE is auto-wrapped in double quotes, so the agent must not quote it itself. It also names the underlying REST call. It stops short of noting rate limits or result-set behavior.

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?

Three short sentences, front-loaded with what the tool does and immediately followed by the auto-quoting constraint and examples. Little waste; the trailing REST endpoint reference is mildly redundant but cheap.

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 read-only, two-param search with no output schema, the description covers mechanism, formatting caveat, and examples. Only the missing routing against freshdesk_list_contacts keeps it from being fully complete.

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%, so both `query` and `page` are already documented in the schema, including the same no-manual-quoting rule. The description's examples add minor value but largely duplicate the schema's own description, so the baseline 3 applies.

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?

States a specific verb (Search) and resource (contacts) plus the mechanism (Freshdesk query DSL), which is far more than a restated title. It does not, however, name the nearest sibling freshdesk_list_contacts or explain how searching differs from listing, so an agent must infer the distinction.

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 examples (`name:'ada'`, `email:'...'`, `company_id:123`) show intended usage patterns and imply this is a filtered lookup, but there is no explicit when-to-use guidance, no statement of when to prefer list_contacts, and no prerequisites or limits called out.

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