get_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 fails to mention pagination behavior beyond the bare schema, rate limits, authentication requirements, or whether this is a safe read operation versus potentially expensive.

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 single sentence is not wasteful, but given 7 parameters, zero annotations, no output schema, and numerous similar sibling tools, it is undersized rather than appropriately concise. Front-loading is impossible with such brevity.

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 tool with 7 filterable parameters and multiple similar siblings, the description is incomplete. It should explain pagination limits, the relationship between filter_id and other filter parameters, and when to prefer search_deals versus this listing endpoint.

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 description coverage, the structured fields already document start/limit pagination and filtering options sufficiently. The description adds no additional parameter context (e.g., that status filters are mutually exclusive with filter_id, or pagination best practices), warranting the baseline score.

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 states the basic action (Get) and resource (deals from Pipedrive), but lacks specificity to distinguish from siblings like get_deal (singular), search_deals, or get_deals_summary. It doesn't clarify if this is a bulk listing operation versus a targeted fetch.

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?

No guidance provided on when to use this tool versus the 6+ sibling deals tools (e.g., search_deals for queries, get_deal for single record retrieval, get_deals_summary for analytics). No mention of prerequisites or filtering recommendations.

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