search_parties

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

No annotations provided; description only mentions default order and lack of sort support. Does not disclose other behaviors like pagination behavior, idempotency, or rate limits. Insufficient for a tool with no annotations.

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?

Two sentences: first succinctly states purpose, second provides alternative tool guidance. No unnecessary words, front-loaded with key information.

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?

Adequate for a simple search tool but lacks output schema and parameter details. The description is minimal and does not cover return format or explicit parameter guidance beyond schema. Moderate completeness given no output schema.

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 50% with only 'q' and 'embed' having descriptions. The overall description does not add meaning for 'page' and 'perPage' beyond their default values and constraints shown in schema. No parameter details in description.

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 it performs free-text search or listing of people and organisations in Capsule CRM. It distinguishes itself from the sibling tool 'filter_parties' by specifying its use case for free-text queries.

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?

Explicitly tells when to use this tool (free-text search/list) and when to use 'filter_parties' for structured queries. Also notes the absence of sort parameter and default ordering.

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