list_deals

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

No annotations exist; description only lists deals and filters, omitting pagination behavior, rate limits, or ordering—key for a list endpoint.

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?

Two sentences with no redundancy, but could be more efficient by integrating pagination info instead of leaving it implicit in the schema.

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?

Despite having an output schema and 4 parameters, the description fails to explain pagination or return behavior, leaving agents underinformed for a list tool with pagination.

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 coverage is 0%; description adds meaning for stage_id and pipeline_id but completely ignores limit and offset parameters, which are critical for pagination.

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?

Clearly states verb 'list' and resource 'deals' with optional filters, distinguishing it from single-deal retrieval tools like get_deal.

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?

Implies listing with optional filters but provides no guidance on when to use vs alternatives (e.g., search_contacts), nor exclusions.

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