hubspot_create_deal

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

The description adds useful non-obvious context: the call routes through the platform's domain-agent dispatcher under JWT/tenant/company scope, which is not present in the annotations. But it does not disclose what side effects occur (e.g., a HubSpot deal record is created externally) or anything about response behavior; annotations carry the read-only/destructive profile.

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 front-loaded with the action name, with no filler. However, the opening sentence is largely a tautology of the tool name, and the argument explanations are so terse that the conciseness comes at the cost of usefulness.

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?

Even with an output schema and annotations, the description is not complete enough to invoke correctly: it lacks the domain meaning of deal creation, the acceptable shape of `inputs`, and when to use the tool versus its siblings. An agent would be guessing about the action's actual behavior.

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 define the parameters, but it only labels `message` as a free-text objective and `inputs` as an optional JSON string. It repeats the type/default information already in the schema and gives no details about what structured input fields are expected for creating a deal.

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 `create_deal`" and describes routing/scope, but never states what a deal is or what creating one does. This is effectively a restatement of the tool name, and it does not distinguish the action from hubspot_create_contact, hubspot_create_campaign, or hubspot_update_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?

There is no guidance on when to choose this tool over hubspot_get_deal, hubspot_search_deals, or the other create_* siblings. The only contextual hint is that `message` is a free-text objective, which does not explain use cases or exclusions.

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