hubspot_create_campaign

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

Annotations already convey destructiveHint=true and idempotentHint=false. The description adds the routing context (through a domain-agent dispatcher under JWT/tenant/company scope) but does not disclose what gets destroyed, what side effects occur, or any authorization context beyond the trivial scope statement.

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, but its first line is a tautology of the tool name. The Args section merely repeats the schema, and the routing/scoping detail is marginal given the context signals. It could have used the space to explain actual campaign creation semantics.

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 destructive side-effect tool with 0% schema coverage, the description is incomplete. It does not explain what a HubSpot campaign is, what inputs the underlying domain action needs, what the response returns, what prerequisites exist, or why the tool is destructive. An agent can make a reasonable guess at best; the description documents the wrapper rather than the tool.

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% and the description only labels the two parameters as 'Free-text objective' and 'Optional JSON string of structured inputs'. It adds almost no meaning: an agent cannot tell what a valid objective is, what structured inputs are accepted by the HubSpot action, what a campaign requires, or what the JSON structure should look like.

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 'Run the hubspot domain agent action create_campaign', which is essentially a restatement of the tool name and adds no insight into what creating a HubSpot campaign actually does. It doesn't mention the entity being created, what a campaign represents, or how it differs from the many other HubSpot create tools.

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?

No guidance is given on when to use this tool versus alternatives like hubspot_create_deal, hubspot_create_workflow, or hubspot_create_form. There is no mention of prerequisites, the domain-agent dispatch mechanism, or when to use the two parameters.

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