List contacts in a Rootr CRM

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description confirms a read-only list operation but adds no new behavioral insights such as pagination details, rate limits, or response structure. It is consistent but not additive.

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 with no redundant information. The first sentence efficiently captures the core purpose and filters, and the second provides valuable context about the CRM node. Every sentence 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?

Given 10 parameters, full schema coverage, and no output schema, the description adequately lists filterable fields and CRM context. However, it omits details on result format, pagination behavior, or sorting defaults, which would be helpful for a complete understanding.

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 100%, so all parameters are documented in the schema. The description reiterates the filter fields (free-text query, company, lifecycle stage, etc.) but adds no additional meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 identifies the tool as listing/searching contacts in Rootr CRM, with explicit mention of filterable fields. It differentiates from sibling tools like rootr_crm_get_contact and rootr_crm_list_companies by specifying 'contacts' within the CRM node.

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 states the tool is for listing contacts with filters, but does not provide explicit when-to-use scenarios or contrast with alternatives such as rootr_crm_get_contact for single contact retrieval. Usage context is implied but not detailed.

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