deals_get_archived_summary

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

No annotations provided, so description carries full burden. It discloses read-only nature (aggregated stats) and filtering behavior. Does not mention rate limits or auth, but for a summary tool the description is adequate.

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?

Well-structured with front-loaded purpose, followed by bullet points for workflow tips and examples. Slightly verbose but every part adds value; could be tightened slightly.

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 no output schema, the description thoroughly explains return values (aggregated stats, counts, values, conversion rates) and covers filtering options and use cases. Complete for a summary tool.

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%, and the description adds value by providing concrete use case examples for each parameter (e.g., 'User archived performance: { "user_id": 123 }'), enhancing understanding beyond the schema.

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 archived deals statistics and summary' and elaborates on returned data (counts by status, total values, conversion rates). It distinguishes from siblings like deals_get_summary (non-archived) and deals_list_archived (list vs summary) through context.

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?

Provides workflow tips and common use cases with specific parameter examples, clearly indicating when to use (historical analysis, reporting). Does not explicitly exclude alternatives, but the context of 'archived' and examples suffice for differentiation.

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