clio_find_contacts

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states that it searches contacts by name or free text, without disclosing details like result ordering, pagination, or whether both clients and parties are included by default. This is minimal context.

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 one short sentence, front-loaded with the verb, resource, and method. Every word earns its place.

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?

With no output schema and no annotations, the description fails to describe return values, result structure, or behavioral limits. The type and limit parameters are unexplained, making the tool underspecified for an agent to use correctly.

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 schema defines three parameters (type, limit, query) with zero description coverage. The description's 'by name or free text' maps to the query parameter but provides no guidance on the type filter or limit behavior. The type enum and limit's default/max are undocumented.

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 states 'Search contacts (clients and parties) by name or free text.' This is a specific verb (search) on a resource (contacts) with a clear scope (clients and parties) and method (name/free text). It distinguishes from siblings like clio_get_contact, which retrieves a single contact.

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 implies usage for searching contacts by name or free text, but does not explicitly state when to use this over alternatives like clio_get_contact or clio_browse. There are no exclusions or alternative recommendations.

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