contacts_query_contacts

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

With no annotations, the description's behavioral disclosure is minimal. It implies a read-only query but does not mention authorization needs, rate limits, pagination behavior (despite a limit parameter), or how multiple filters combine.

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 concise with a clear first-sentence purpose followed by a well-structured parameter list. It efficiently conveys all necessary information without extraneous text.

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 presence of an output schema, return value details are not required. However, the description omits behavioral details like default sort order, interaction between filters (AND/OR), and behavior when no results are found. It is adequate for a simple query tool but not comprehensive.

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 description coverage is 0%, so the description compensates by explaining each parameter's role (e.g., 'Filter to contacts in this address book', 'Full-text search across name, email, phone, etc.'). The explanations are clear and add value beyond the schema type definitions.

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 'Query contacts with optional filters and sorting', specifying the verb (query) and resource (contacts). It distinguishes from sibling tools like contacts_get_contact (single contact) and contacts_list (likely a simple list) by mentioning filters and sorting.

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 tool versus alternatives such as contacts_list or contacts_get_contact. There is no mention of prerequisites, when not to use, or typical scenarios.

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