deals_get_summary

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

No annotations are provided, so the description must convey behavioral traits. It states the tool returns aggregated statistics, implying a read-only operation. However, it does not explicitly mention that no data is modified, nor does it address potential limitations (e.g., rate limiting, permissions).

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 description is well-structured with sections for workflow tips and common use cases. It is concise enough to convey key information without unnecessary detail. A slight improvement could be combining the tips and use cases into a more compact format.

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 the tool's simplicity (4 optional parameters, no output schema), the description adequately covers what the tool does and what it returns (counts, values, conversion rates). It provides enough context for an AI agent to use it effectively for dashboards and reporting.

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?

The input schema already has 100% description coverage with clear parameter definitions. The description adds value by showing common use case combinations (e.g., using user_id and stage_id together), which helps the agent understand how to leverage parameters effectively beyond their individual meaning.

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 'Get deal statistics and summary' and specifies aggregated statistics like counts by status, total values, and conversion rates. It distinguishes from sibling tools like deals_list or deals_get by focusing on summary rather than individual deals.

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 provides workflow tips and common use cases with parameter examples, guiding the agent on when to use specific filters (e.g., user_id for user performance, stage_id for pipeline analysis). It covers context but does not explicitly exclude scenarios where this tool should not be used.

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