list_contacts

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states 'List contacts' without describing pagination behavior, ordering, filtering beyond scoping, or whether results are limited. The existence of an output schema may partially compensate, but the description adds little 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 very concise at two sentences, no wasted words. However, it is perhaps too brief to fully inform the agent, but the conciseness is otherwise commendable.

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 6 optional parameters and the presence of an output schema, the description is incomplete. It fails to explain core features like pagination, field selection, sorting, or the overall shape of the response. The agent may need to infer from the schema, but the description should provide more context.

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 coverage is 100%, so baseline is 3. The description adds context by mentioning customer_id and supplier_id as typical scoping parameters, but does not elaborate on sort, fields, or pagination parameters. It adds marginal value over the schema.

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 clearly states the action 'list' and resource 'contacts', and hints at typical scoping by customer_id or supplier_id. However, it does not explicitly differentiate from sibling listing tools like list_customers or list_suppliers.

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 minimal usage guidance by suggesting to scope to a customer_id or supplier_id. It does not mention when not to use or alternatives, but the hint is useful.

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