hubspot_plan_domain_intelligence

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

Annotations already flag destructiveHint=true, readOnlyHint=false, and openWorldHint=true. The description adds useful context that execution routes through the platform's domain-agent dispatcher under JWT, tenant, and company scope. However, it does not disclose what side effects may occur or why the action is considered potentially destructive.

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, followed by routing scope and an Args section. There is no filler, though the first line is close to a restatement of the tool name and the functional description is thin.

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 domain-agent action with vague parameters, no usage conditions, and a potentially destructive flag, the description is insufficient for confident invocation. The output schema exists, but the description still fails to explain what objective should be supplied, what structured inputs look like, or what outcomes the agent should expect.

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 does add basic meaning: 'message' is a free-text objective and 'inputs' is an optional JSON string. But it provides no structure, allowed keys, examples, or constraints for the JSON string, leaving the most important input under-specified.

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 ('plan_domain_intelligence'), a specific agent ('hubspot domain agent'), and a routing path, which makes the tool's target identifiable. However, it never explains what planning domain intelligence actually accomplishes, so an agent knows which action fires but not its functional purpose.

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 such as dispatch_domain_agent, list_domain_actions, or the many sibling '*_plan_domain_intelligence' tools. The description implies a single use case but provides no context, exclusions, or selection criteria.

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