hubspot_recent_won_deals

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

Since no annotations are provided, the description must disclose behavioral traits. It correctly identifies the tool as READ-ONLY and explains automatic stage filtering. However, it lacks details on pagination, rate limits, or required 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 front-loaded with the core purpose and ordering. It efficiently conveys usage and parameter info without redundancy, though the warning paragraph could be slightly tighter.

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?

The description covers the key aspects: purpose, ordering, usage guidelines, parameter meanings. The presence of an output schema reduces the need to describe return values. It could explicitly state sorting direction, but it's implied.

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 0% schema coverage, the description compensates well by explaining both parameters with types, defaults, and usage notes. The only gap is not specifying allowed values for properties beyond the default.

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 tool retrieves 'most recently CLOSED-WON deals' with explicit ordering by close date. It distinguishes from sibling tools like hubspot_search_deals by specifying the filtered subset and automatic stage resolution.

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 explicit use cases ('recent/last/latest closed-won deals') and warns against misusing lifecyclestage. It explains the automation of filtering but does not explicitly contrast with similar deal search tools, leaving some ambiguity.

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