hubspot_list_deals

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

No annotations are provided, so the description bears full responsibility. It only states 'list' and 'pagination', but does not disclose that it is a read operation, how pagination works (e.g., using 'after' cursor), rate limits, or what the default return set is. Significant behavioral details are missing.

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 a single sentence, concise and direct, with no wasted words. It efficiently conveys the core action and key feature (pagination). Could include a bit more context without becoming verbose.

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 tool has 3 optional parameters, no required parameters, and no output schema. The description is minimal but covers the basic purpose. However, it lacks information about the output format, default properties, or next page cursor. For a simple list operation, it is adequate but incomplete.

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%, with each parameter having a clear description (e.g., after: 'Pagination cursor for next page'). The tool description adds no additional meaning beyond the schema, so baseline score of 3 is 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 clearly states the action ('List') and resource ('deals from HubSpot'), and mentions pagination. It distinguishes from sibling tools like hubspot_get_deal (single deal) and hubspot_search_deals (search with filters). However, it does not elaborate on the scope or differentiate among similar list tools (e.g., list vs search).

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?

No guidance is provided on when to use this tool versus alternatives like hubspot_search_deals or hubspot_get_deal. There is no mention of when to paginate or any exclusions. The description simply states the action without usage context.

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