hubspot_create_form

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

Annotations already mark this as non-read-only, non-idempotent, and destructive, so the description is not the only source of safety information. It adds useful scoping context (JWT, tenant, company) and mentions it routes through the domain-agent dispatcher, but it does not describe the concrete effects of the action.

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 front-loads the primary purpose before adding routing context and parameter notes. The Args block is compact and adds value over the bare schema.

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 having an output schema and annotations, the description is incomplete for a tool that wraps a domain-agent action: it never says what a HubSpot form is, what data is needed, or how message/inputs should be populated for a successful create_form call. The large sibling list makes this ambiguity more costly.

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?

With 0% schema description coverage, the Args section carries the documentation burden, and it does provide some semantics: message is a free-text objective and inputs is an optional JSON string. However, it does not explain what structured inputs are expected or how the message should be phrased, leaving substantial ambiguity.

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 only says 'Run the hubspot domain agent action create_form,' which restates the tool name without explaining what creating a form involves or what the action produces. It does not distinguish from sibling tools like hubspot_create_deal or hubspot_create_contact beyond the action name embedded in the tool 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?

No guidance is given about when to choose this tool over alternatives, such as hubspot_create_campaign or hubspot_create_workflow. The routing/scope note explains how execution happens, not when the tool is appropriate.

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