hubspot_create_deal

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

With no annotations provided, the description bears full responsibility. It only states the creation action, omitting critical behavioral details such as side effects, authentication requirements, rate limits, or the return value (e.g., deal ID). This is insufficient for a mutation 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 two short sentences, no wasted words. However, it is so brief that it sacrifices important context. It is well-structured but could benefit from a sentence about return value or required fields.

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?

Given the complexity of a nested 'properties' parameter with 7 fields and no output schema, the description is incomplete. It does not explain which properties are required by HubSpot, date format expectations, or what the tool returns upon success.

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 input schema covers 100% of parameters with its description listing the fields, so the schema already provides parameter semantics. The description adds value by pointing to hubspot_get_pipelines, which helps the agent understand valid values for pipeline and dealstage.

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 'Create a new deal in HubSpot' clearly states the action (verb 'create') and resource ('new deal'), directly matching the tool name. It distinguishes from sibling tools like hubspot_update_deal and hubspot_delete_deal.

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 provides a helpful guideline: 'Use hubspot_get_pipelines to see available pipelines and stages,' which informs the agent when to prepare by querying valid values. However, it does not explicitly contrast with alternatives or state when not to use this tool.

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