List companies in a Rootr CRM

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

Annotations already mark the tool as readOnlyHint=true and destructiveHint=false. The description adds context about filtering, sorting, and pagination, but does not disclose any behavioral traits beyond what annotations provide. It is consistent but does not add significant new behavioral insights.

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 only two sentences, with no wasted words. The first sentence is compact and front-loaded with the core purpose. The second sentence adds context about the CRM capabilities without being verbose.

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?

While the tool has annotations and a rich input schema, it has no output schema, so the description should ideally explain the return value structure. It mentions filtering and pagination but does not describe what the output contains (e.g., list of company objects). This leaves a gap for the agent.

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?

With 100% schema coverage, baseline is 3. The description adds value by summarizing the filtering options ('optionally filtered by free-text query, owner, or tag, and sorted/paginated'), providing a concise overview that complements the individual parameter descriptions.

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's purpose: 'List/search companies in a Rootr CRM, optionally filtered... sorted/paginated.' This specific verb+resource combination distinguishes it from sibling tools like rootr_crm_list_contacts or rootr_crm_list_deals.

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 provides clear context that this tool is for companies within a CRM node, but it does not explicitly state when to use this tool vs alternatives (e.g., rootr_crm_list_contacts for contacts) or when not to use it. The usage is implied but not explicit.

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