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

The annotations already declare readOnlyHint=true, and the description adds the HTTP GET method, which reinforces the non-destructive nature. However, it does not disclose pagination defaults, response format, or any rate-limit behavior, but with annotations present, this is a minimal acceptable disclosure.

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 one short sentence plus the REST path, with zero filler or redundant information. It is front-loaded and entirely focused on the core purpose, making it highly efficient.

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?

With a read-only annotation and fully self-documenting parameters, the description is minimally adequate. However, it lacks any mention of the return format or pagination behavior, and the absence of an output schema means the agent relies on assumptions about the response structure. This is a clear gap, though not severe for a straightforward list endpoint.

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 input schema provides full descriptions for all 8 parameters (100% coverage), so the description does not need to elaborate. The description's generic 'List/filter contacts' adds no specific parameter detail, but the baseline score of 3 is appropriate because the schema does the heavy lifting.

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 states 'List/filter contacts' with a specific resource and verb, and includes the REST endpoint GET /contacts. It clearly identifies the operation but does not explicitly distinguish itself from sibling freshdesk_search_contacts, which also lists contacts with filters.

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 no guidance on when to use this tool versus alternatives like freshdesk_search_contacts. It only states the basic list/filter capability, leaving the agent to infer usage from the endpoint and filter parameters.

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