hs_get_deal

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

With no annotations, the description does a good job. It indicates a read operation ('retrieve') and mentions specific fields returned. Although no output schema exists, the listed fields provide adequate transparency for a simple get-by-ID tool.

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 with no wasted words. It efficiently conveys the tool's purpose and key return data.

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?

For a simple get-by-ID tool with one parameter and no output schema, the description is fairly complete. It specifies what is retrieved and key fields. Minor gaps: could mention how the dealId is obtained, but not critical.

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 covers the only parameter (dealId) at 100%. The description adds no additional meaning beyond the schema's 'HubSpot deal ID'. For a single simple parameter, this is sufficient.

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 a single deal by ID and lists key fields (amount, stage, close date, contacts/companies). It distinguishes from siblings like hs_search_deals (search multiple) and hs_deals_by_stage (filtered).

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 when to use (need a single deal by ID) but does not explicitly state when not to use or suggest alternatives. Siblings are available, so the context is clear enough.

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