hubspot_get_deal

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

Annotations already carry the safety profile (readOnlyHint=false, destructiveHint=true), and the description adds only generic dispatcher/auth context. It does not clarify why a get_deal action is marked destructive or whether it can mutate data, which is a notable gap given the tool's read-only-sounding name.

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 short and the Args section is clean and front-loaded. However, the opening sentence largely echoes the tool name and the overall content is thin, so brevity is achieved at the expense of substance.

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?

Despite an output schema existing, the description leaves the agent without enough information to invoke the action correctly: it doesn't define the action's semantics, expected inputs, or how it differs from search_deals/get_workflow. For a destructive-capable dispatcher wrapper, this is 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 0%, so the description must compensate. The Args section offers only generic definitions: message is a 'free-text objective' and inputs is an 'Optional JSON string of structured inputs'. It does not explain what structured inputs get_deal expects (e.g., the deal identifier) or how the message should be phrased.

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 says only 'Run the hubspot domain agent action `get_deal`', which restates the tool name without explaining what a get_deal action actually does. It never states that this retrieves a specific HubSpot deal or what resource/ID it targets, leaving the agent to infer behavior from the name.

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 gives routing/scope context ('Routes through the platform's domain-agent dispatcher under your JWT, tenant, and company scope') but no guidance on when to select this tool over siblings like hubspot_search_deals or list_crm_deals. No alternatives or exclusions are mentioned.

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