hubspot_list_marketing_events

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

The description provides no behavioral details. The annotations indicate destructiveHint=true, which is surprising for a list operation, and the description does not clarify any side effects or destructive actions. No additional context is given about what might be affected.

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 very concise, with two clear sentences. No fluff or redundant information. It is well-structured and easy to read.

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?

The description lacks critical context: no output schema or return value description, no examples, no details on how to use the parameters effectively. For a simple list tool, it is still incomplete given the vague parameter descriptions and absence of behavioral notes.

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?

The schema has no descriptions (0% coverage), so the description must compensate. It only says 'message' is a free-text objective and 'inputs' is an optional JSON string, which is generic and does not explain expected values or structure. Minimal semantic help.

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 states the tool runs the 'list_marketing_events' action, clearly indicating it lists marketing events. The mention of routing through a dispatcher adds context but not necessary. It does not explicitly differentiate from other list tools, but the name is specific enough.

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 versus alternatives. It does not mention conditions, exclusions, or scenarios where this tool is preferred over other list tools.

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