list_quotes

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

No annotations are provided, so the description must disclose behavioral traits. It reveals that the tool is a read operation (list) and that it can filter by deal_id. However, it does not mention pagination, rate limits, or potential side effects. The description is adequate but not rich; it adds some value beyond the schema.

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 two sentences long and efficiently conveys the purpose, optional filter, and return fields. Every sentence contributes meaningful information without redundancy or fluff.

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 core functionality: listing quotes with optional filtering. An output schema exists, so return values are documented there. However, it lacks details on pagination or sorting behavior, which would be helpful for a complete understanding of the tool's behavior.

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 schema has 0% description coverage, so the description must compensate. It explains the 'deal_id' parameter's purpose (optional filter) but does not describe the 'limit' parameter. This is a gap, as both parameters go uncommented in the schema. The description adds partial value but is insufficient for full understanding.

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 HubSpot quotes') and the resource ('quotes'). It specifies optional filtering by deal_id and lists the returned fields (title, status, expiration, amount). This distinguishes it clearly from sibling tools like get_quote (singular retrieval) and search tools.

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 indicates when to use this tool: to list quotes, optionally filtered by deal_id. It implies a listing scenario, but does not explicitly state when not to use it or mention alternatives. However, the sibling tool get_quote covers singular retrieval, providing implicit guidance.

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