list_crm_contacts

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states that the tool lists contacts and can filter by search. It fails to mention pagination behavior, sorting, rate limits, or any side effects. This is insufficient for an agent to predict behavior reliably.

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 at two sentences plus an Args list. The key information is front-loaded. It wastes no words, though the Args list could be integrated more elegantly.

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?

For a simple list tool, the description covers basic purpose and parameters. However, it omits important details like pagination, default behavior without search, and whether sorting is supported. An output schema exists, so return values are covered externally, but behavioral gaps remain.

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, so the description must compensate. It adds meaning by explaining 'search' as a filter and 'limit' as 'Max results (default 20)'. This goes beyond the schema's raw type and default, providing practical semantics.

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 CRM contacts and mentions optional filtering. The verb 'list' and resource 'CRM contacts' are specific, and it distinguishes itself from sibling tools by being a generic CRM contact lister rather than a specific platform variant.

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 mentions optional search filtering and a limit parameter, implying usage scenarios. However, it does not explicitly state when to use this tool over similar sibling tools (e.g., clio_list_contacts, freshbooks_list_clients), nor does it provide when-not-to-use guidance.

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