pipedrive_deals_summary

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

No annotations are provided, so the description must disclose behavior. It states the tool returns a 'Claude-friendly' snapshot and mentions stage counts for overviews. However, it does not specify the exact output format, any side effects (though likely read-only), or rate limits. The description provides basic transparency but lacks detail.

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 well-structured sentences with the key information front-loaded. No redundant or verbose text. Every sentence serves a purpose.

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 10 parameters, no output schema, and no annotations, the description is incomplete. It does not explain filtering options, pipeline selection in overview mode, or the output format. Important behavioral aspects are missing, making the tool less predictable for an AI 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 10 parameters and 0% schema description coverage, the description only adds meaning for deal_id and the three inclusion flags. The other six parameters (owner_id, person_id, org_id, pipeline_id, stage_id, status) are not mentioned, leaving their purpose unknown. This insufficiently compensates for the schema gaps.

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 verb (Get) and resource (deal or pipeline snapshot), distinguishes between two distinct modes (single deal vs pipeline overview), and specifies optional inclusions. This effectively differentiates from sibling tools like pipedrive_deals_get.

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 explicitly instructs when to use each mode: 'Pass deal_id for a single deal summary... Omit deal_id for a pipeline overview.' This provides clear context. However, it does not explicitly mention when to avoid using this tool in favor of alternatives like pipedrive_deals_list or pipedrive_deals_search.

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