hubspot_create_import

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

The description adds routing and authorization context ('under your JWT, tenant, and company scope'), which is useful beyond the annotations. However, it does not disclose the side effects, the delegated nature of the agent action, or what the destructive hint implies. The description does not contradict the annotations, so this is not an annotation contradiction.

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, front-loaded with the action name and routing context, and lists arguments cleanly. The opening sentence largely repeats the tool name, and the brevity comes at the cost of substantive guidance, but there is no filler or wasted wording.

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 though an output schema exists, the description leaves out the domain semantics of create_import, the expected structure of inputs, and what behavior to expect after invocation. For a mutating, open-world domain-agent action, the agent lacks enough information to know what to put in message or inputs and what side effects will occur.

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 description does add basic meaning by labeling message as a 'free-text objective' and inputs as an 'optional JSON string of structured inputs.' However, it gives no details about what a valid create_import objective or input JSON should contain, leaving the parameters largely opaque for constructing a correct call.

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_import' and describes routing through a dispatcher; it never states what create_import actually does, such as importing data into HubSpot. This essentially restates the tool name without explaining the resource, effect, or output, and it does not distinguish this tool from sibling hubspot_create_* wrappers.

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 use this tool versus alternatives like hubspot_passthrough, dispatch_domain_agent, or hubspot_list_imports. The only implied context comes from the tool name itself; there are no exclusions, prerequisites, or alternative conditions stated.

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