list_contacts

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

With no annotations, the description carries the burden of behavioral disclosure. It states pagination support, which is a key behavior, but does not clarify return format, ordering, or whether soft-deleted contacts are included. For a simple read tool, this is some disclosure but leaves gaps.

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 a single, front-loaded sentence with no wasted words. It efficiently conveys the core functionality and pagination aspect.

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 simple list operation with two optional parameters, the description is minimally adequate but lacks details such as response structure (no output schema), maximum per_page allowed, or any filtering caveats. It is not misleading but leaves room for misinterpretation in edge cases.

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 provides zero descriptions for 'page' and 'per_page', and the description only says 'with pagination support' without defining these parameters. This does not sufficiently compensate for the 0% schema coverage, leaving the agent to infer the meaning of the parameters from defaults and names.

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 action ('List') and the resource ('all contacts in Freshdesk'), distinguishing it from siblings like 'search_contacts' (search vs. list) and 'get_contact' (single vs. all). It also indicates pagination scope, making the purpose unambiguous.

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 phrase 'List all contacts' implies a use case for bulk enumeration, but there is no explicit guidance on when to use this tool versus alternatives like 'search_contacts'. It does not mention exclusions or prerequisites, so the usage is only implicitly communicated.

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