hubspot_emit_behavioral_event

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

Annotations already convey mutability and destructiveness, so the description need not restate them. It adds useful routing and JWT/tenant/company scoping context, but it doesn't disclose what side effects occur or what actually changes in HubSpot.

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 logically structured, front-loading the action, then routing, then parameters. It has almost no filler, though the first sentence is somewhat redundant with the tool name.

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 a destructive, non-idempotent action with ambiguous domain meaning, the description is too thin: it lacks business context, event semantics, and input-shape guidance. The output schema and annotations help, but an agent still cannot tell when or how to formulate a valid behavioral event.

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 zero schema description coverage, the Args section gives minimal semantics: message is a free-text objective and inputs is an optional JSON string. This is helpful but vague, with no structure, examples, or allowed keys for the JSON.

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 names a specific action and routing path but never explains what a behavioral event is or what effect emitting one has in HubSpot. The first sentence largely restates the tool name, so the domain purpose is left to inference.

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 provided on when to use this tool versus alternatives such as hubspot_passthrough, hubspot_create_timeline_event, or dispatch_domain_agent. The routing-through-dispatcher note explains mechanics, not selection criteria.

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