hubspot_list_marketing_emails

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

The description claims a 'list' action, which implies read-only behavior, while annotations declare destructiveHint=true and readOnlyHint=false. This is a direct contradiction, and the description provides no clarification about side effects, so the behavioral trait is misleading.

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 has a clean structure: action, routing context, then args. However, most of its content is generic wrapper boilerplate rather than tool-specific detail, so the conciseness does not fully compensate for low information density.

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?

Although an output schema exists, the description is too thin for an agent to confidently invoke this tool: it doesn't explain what listing marketing emails means, what the expected 'inputs' should look like for HubSpot, or how the action behaves. The routing/auth details are useful but do not make the definition complete.

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 adds important meaning by explaining that 'message' is a free-text objective and 'inputs' is an optional JSON string of structured inputs. However, it stops short of describing what structured inputs are expected for the underlying HubSpot action, 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 to run the 'list_marketing_emails' action, essentially restating the tool name. It does not state what the action does, what it returns, or how it's distinguished from sibling HubSpot list tools, making it close to a tautology.

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 compared to alternatives such as hubspot_list_campaigns, hubspot_list_forms, or other HubSpot listing tools. There is no mention of conditions, filters, or use cases that would help an agent select this tool.

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