list_contacts

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly implies a read-only listing operation and explains output_format and save_to_file side effects, but it does not explicitly state non-destructive behavior or address authentication, rate limits, or result truncation.

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 compact and well structured: a clear one-line purpose, a bulleted Args list, and a one-line Returns statement. There is no filler or unnecessary repetition of schema defaults.

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 10-parameter list tool with no annotations, the description documents every parameter and the return type. It does not specify whether filters combine with AND or OR, nor does it explain when to choose this over search_contacts, which leaves minor usability 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?

Schema description coverage is 0%, so the parameter descriptions provide the only meaningful semantics beyond names and types. Every parameter is explained with its purpose, including partial-match behavior, pagination, output format choices, and the save_to_file behavior.

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 opens with 'List contacts from IT Glue', stating a specific verb and resource, and further clarifies the filter dimensions. It does not explicitly contrast with sibling search_contacts, so an agent must infer the difference between a broad listing and a targeted search.

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?

There is no guidance on when to use list_contacts versus search_contacts or get_contact. The pagination and filter parameters imply a list workflow, but the description does not state when this tool should be preferred or when an alternative is more appropriate.

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