list_contacts

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

No annotations are provided, so the description must convey behavioral details. It states 'List all contacts' but the schema includes pagination params (per_page default 50), suggesting results are paginated, which creates potential ambiguity about whether 'all' means one page or all pages. The description does not mention return format, potential size, or any side effects, offering minimal transparency.

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 sentence with zero wasted words. It front-loads the action 'List' and clearly specifies the resource, making it highly efficient and well-structured.

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?

This is a simple list tool with complete parameter documentation and clear purpose, making the description minimally adequate. However, there is no output schema and the description does not explain the return structure or pagination behavior, leaving some gaps for a fully complete contextual picture.

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% for both parameters (page and per_page), so the schema already documents their meaning. The description adds no additional semantics beyond what the schema provides, warranting the baseline score of 3.

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 uses a specific verb 'list' with a clear resource 'contacts' and scope 'in the organization'. This clearly distinguishes it from sibling tools like get_contact (single contact) and create_contact (creation), so purpose is 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 description implies usage when all contacts are needed, but provides no explicit context about when to use this tool versus alternatives like get_contact or search tools. There are no exclusions or alternative recommendations, leaving the agent to infer usage from the tool name alone.

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