list_contacts

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

No annotations are present, so the description bears full responsibility for behavioral disclosure. It fails to mention any traits such as pagination, rate limits, ordering, or whether the list includes all contact details or just summaries. The description is too brief to ensure informed usage.

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 extremely concise at two words. It front-loads the core action without waste. However, it sacrifices necessary detail for brevity, so it does not perfectly earn its place given the lack of behavioral and usage context.

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 no parameters, no output schema, and no annotations, the description is insufficient for complete understanding. It omits crucial context like pagination, return format, or whether the list is limited to the current account. A more complete description would clarify these aspects.

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?

There are zero parameters and schema description coverage is 100%. Per guidelines, 0 parameters yields a baseline of 4. The description adds no parameter info, but none is needed since there are none.

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 'List all contacts' uses a specific verb ('list') and resource ('contacts'), clearly distinguishing it from sibling tools like 'get_contact' (singular) and 'create_contact'. It states the exact scope (all contacts) without ambiguity.

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 on when to use this tool versus alternatives is provided. While the zero-parameter nature makes it straightforward, there is no mention of filtering, sorting, or when one might prefer a different tool (e.g., searching). Usage is implied but not explicitly guided.

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