list_contacts

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

No annotations are provided, so the description must fully disclose behavior. It mentions filtering options but fails to describe pagination behavior (page, per_page), default ordering, or any side effects. For a listing endpoint, these are significant gaps.

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 two sentences plus an additional clarifying sentence for the fuzzy search. It is front-loaded with the main purpose and filters, then usage guidance. No unnecessary words.

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 has 5 parameters, no annotations, and an output schema, the description covers the core functionality and usage context. However, it lacks explanation of pagination behavior, which is important for listing tools. The output schema likely describes return values, so that aspect is covered.

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 0% description coverage, but the description explains three parameters (status, tag_ids, q) and details what the fuzzy search matches. However, it completely omits page and per_page, leaving pagination parameters undocumented. With low schema coverage, the description should explain all parameters.

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 tool lists addressbook contacts with optional filters. It also specifies a concrete use case (finding a numeric ID for find_serving_pattern). However, it does not explicitly differentiate from sibling list tools like list_ministry_members or list_ministries.

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 explicit usage guidance: 'Use this to find a contact's numeric ID... for use with find_serving_pattern.' This gives clear context for when to use it, but it does not mention when not to use it or list alternatives.

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