Update HubSpot Deal

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

The description explicitly states 'Only provided fields are changed,' indicating partial update behavior. Annotations confirm it is not read-only (readOnlyHint=false) and not destructive (destructiveHint=false), with idempotency (idempotentHint=true). No contradictions exist. The description adds value by clarifying the partial update nature.

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 compact and well-structured: a concise purpose sentence, bulleted use cases, and clear Args/Returns sections. Every sentence is informative, with no 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?

With full schema coverage and clear annotations, the description covers core functionality. However, it lacks details about return value structure (no output schema), error handling, or prerequisites like permissions. For a mutation tool, these omissions leave some gaps.

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%, so baseline is 3. The description adds meaning by giving concrete examples of parameter usage (e.g., 'update dealstage' for moving stages, 'hubspot_owner_id' for reassignment). This helps an agent understand common patterns beyond the raw schema.

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 updates properties on an existing HubSpot deal. It distinguishes from sibling creation and deletion tools, though it does not explicitly differentiate from other update tools like hubspot_update_company. The purpose is specific and actionable.

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?

Common use cases are provided (moving deal stage, updating close date, reassigning owner), giving practical guidance. However, it lacks explicit when-not-to-use instructions or context of alternatives (e.g., when to create vs. update). The first line mentions 'existing deal,' which implies the deal must already exist.

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