list_crm_deals

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only describes the basic operation and parameters without mentioning any behavioral traits such as read-only nature, rate limits, or side effects. As a listing tool, it is likely safe, but that is not stated.

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 extremely concise: two sentences that immediately state the purpose and list the parameters. No extraneous words or redundant information. It is well front-loaded with the core action.

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 the tool's simplicity (two optional parameters) and the presence of an output schema, the description covers the essential context. It clearly states what the tool does and how to use its parameters. Some detail about filtering or pagination is missing but not critical for a basic list operation.

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 description adds meaning beyond the schema by describing 'search' as an 'Optional search term' and 'limit' as 'Max results (default 20)'. The schema has 0% description coverage, so these clarifications are valuable and compensate for the lack of schema-level documentation.

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 action ('List') and the resource ('CRM deals/opportunities'). It uses a specific verb and resource, distinguishing it from other list tools that operate on different CRM entities like contacts or tasks.

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 that this tool should be used when listing CRM deals but provides no explicit guidance on when to use it over alternatives, nor any when-not-to-use conditions. No sibling differentiation is offered beyond the resource name.

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