list_contacts

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 covered. However, the description adds no behavioral context beyond 'fetching a list'—no mention of pagination defaults, archive inclusion behavior, or ordering specifics. It fails to disclose any traits beyond what the annotations and schema already 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 a single, concise sentence that directly states the action and object. It contains no unnecessary words or filler, making it highly succinct and perfectly front-loaded.

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, the schema documents all parameters and the annotations cover safety, making the tool usable. However, the description omits differentiating context from search_contacts, and with no output schema, it does not explain the return structure or default pagination. The definition is adequate but leaves some 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?

All four parameters (limit, offset, order_by, show_archived) have detailed schema descriptions covering their semantics, giving 100% schema coverage. The description 'Fetch a list of contacts' adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.

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 'Fetch a list of contacts' clearly specifies a verb and resource, indicating the tool retrieves a collection of contacts. However, it does not distinguish this from the sibling 'search_contacts' tool, which likely also returns contacts, so it lacks explicit differentiation.

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 provides no guidance on when to use this tool versus alternatives such as 'search_contacts' or 'get_contact'. There is no mention of scenarios like listing all contacts versus searching with filters, leaving the agent to infer the appropriate use case.

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