get_quote

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

With no annotations provided, the description carries the full burden. It states the tool retrieves details (implying a read-only operation), but it does not disclose potential errors (e.g., invalid ID), authentication requirements, or data refresh behavior. The transparency is minimal but sufficient for a simple read operation.

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, front-loaded sentence that efficiently conveys the tool's purpose and scope. No extraneous information is present.

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 is short but covers the essential action and mentions line items. Given that an output schema exists, the return values are already defined elsewhere. The description provides enough context for an agent to understand the tool's basic function, though it could hint at input format or error handling.

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 0%, so the description must compensate. However, the description only restates that the quote is identified 'by its id' without adding format, length, or example values for the 'quote_id' parameter. This adds little value beyond the schema field name.

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 ('Get full details'), the resource ('a single HubSpot quote'), the identifier method ('by its id'), and what additional data is included ('including line items'). This effectively distinguishes it from sibling tools like 'list_quotes' (listing multiple) and 'search_quotes' (search-based retrieval).

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 implies use when you have a specific quote id, but it provides no explicit guidance on when to use this tool versus alternatives (e.g., list_quotes for browsing, search_quotes for filtering). No conditions or prerequisites are mentioned, which is adequate but not exemplary.

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