pipedrive_my_pipeline_summary

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

With no annotations provided, the description carries the full behavioral burden. It does disclose the output nature (aggregated deal counts and values by stage), which is useful, but it omits any safety profile, permissions needed, or whether the operation is read-only, leaving gaps for a tool with zero annotation coverage.

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?

A single, front-loaded sentence that states scope and output with no wasted words. It is efficient, though it crams scope and return content into one clause without further structuring.

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 read-only, two-parameter summary tool with no output schema, the description adequately conveys what is returned (counts and values by stage) and the user scoping. There is no output schema, so explaining the return content in prose is the right call, and it does so.

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 description coverage is 100%, so both parameters (as_user, pipeline_id) are already fully documented in the schema. The description only references them obliquely ('current user (or as_user)', 'by stage') and adds no syntax or default detail beyond the schema, making the baseline 3 appropriate.

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 names a specific resource (pipeline snapshot) scoped to the current user and states the returned content (deal counts and values by stage). It is clearly distinguishable from generic list tools, though it does not explicitly contrast itself with the sibling pipedrive_deals_summary.

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 says what the tool produces but gives no when-to-use guidance, no conditions for choosing it over siblings like pipedrive_deals_summary or pipedrive_my_open_deals, and no exclusions. The only hint about usage is the parenthetical 'or as_user', which the schema already covers.

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