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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds that the tool returns specific fields and mentions 'filtering and pagination,' which is consistent with the parameters. However, it does not disclose additional behavioral traits beyond what annotations and schema already convey.

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 that concisely states the purpose and key outputs. Every word earns its place; there is no fluff 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?

For a simple list tool with well-documented parameters and annotations, the description is mostly complete. It covers the action, returned fields, and hints at pagination. However, it omits that without filters it returns the first page of all contacts, which could be clarified. Given the existing output schema, this is a minor gap.

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 description coverage is 100%, so each parameter (page, _apiKey, _domain, per_page) is already documented. The description mentions 'filtering and pagination' but does not add new meaning to the parameters; it only hints at the output. Per the guidelines, baseline 3 is appropriate when the schema already fully describes parameters.

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 lists customer contacts and enumerates returned fields (name, email, phone, company, contact ID). It uses a specific verb and resource, which distinguishes it from sibling tools like 'freshdesk_get_contact' that retrieve a single contact. However, it could be more explicit about whether it lists all contacts or supports search filtering.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not mention that 'freshdesk_get_contact' should be used for a single contact or that 'freshdesk_search_tickets' handles tickets. The agent has no explicit context for choosing this tool over siblings.

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