list_all_secondary_contacts

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

Annotations already declare the tool as read-only and non-destructive. The description adds 'Fetches data. Makes no changes' and includes an emoji indicator, but does not elaborate on pagination behavior or API specifics beyond what annotations provide.

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 short but contains redundancy: 'List all secondary contacts' appears twice and 'Retrieve all secondary contacts' repeats the same idea. It could be more concise by eliminating duplication.

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?

Given the tool's low complexity, rich annotations, and full schema coverage, the description is adequate. However, it fails to clarify that 'all' is paginated (implied by limit/offset) and lacks guidance on when to use list vs retrieve.

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 has 100% coverage with detailed descriptions for all four parameters (limit, offset, orders, filters). The tool description adds no additional parameter information, so it meets the baseline without extra value.

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 explicitly states 'List all secondary contacts' and 'Retrieve all secondary contacts', clearly indicating the action and resource. The tool name is self-explanatory, and it distinguishes from sibling 'retrieve_a_secondary_contact' which targets a single contact.

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 listing tool versus the singular retrieval or other alternatives. The description only states its read-only nature, missing context on pagination or selection criteria.

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