pipedrive_deals_summary

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

With no annotations, the description carries the full burden. 'Get' implies a read, and it discloses what each mode returns (stage counts; optional activities/notes/products), but says nothing about permissions, rate limits, pagination, or result size for a 10-parameter aggregation tool.

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?

Three tight sentences, front-loaded with the tool's purpose before the mode-switching detail. Every sentence carries information; no filler.

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 10-parameter tool with no annotations and no output schema, the description explains the two modes and the optional includes but leaves most filter parameters and the response shape unaddressed. Adequate minimum, but gaps remain that an agent must probe.

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 only 20%, so six-plus parameters (org_id, status, stage_id, person_id, pipeline_id, include_recent_activities) have no documentation anywhere. The description adds meaning for deal_id and the include_* flags ('with optional activities/notes/products'), partially compensating, but the filter parameters remain unexplained.

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 a specific verb and resource ('Get a Claude-friendly deal or pipeline snapshot') and clearly delineates two operating modes based on deal_id. It does not, however, differentiate itself from close siblings such as pipedrive_deals_get or pipedrive_my_pipeline_summary, leaving the agent to infer which summary tool applies.

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?

It gives explicit mode-selection guidance: pass deal_id for a single-deal summary, omit it for a pipeline overview. That covers internal branching but offers no cross-tool guidance, no mention of when to prefer pipedrive_deals_get, pipedrive_my_pipeline_summary, or pipedrive_deals_list instead.

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