hubspot_list_owners

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

The description does not disclose any side effects, permission requirements, or behavior beyond 'routes through the dispatcher'. Given the destructiveHint annotation is true, the lack of any mention of destructive potential is a significant transparency gap.

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 but not well-structured. It repeats generic dispatcher information and lacks specific details about list_owners. While concise, it sacrifices clarity and usefulness.

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?

There is no output schema, no details about the expected inputs, and no differentiation from dozens of sibling tools. The description is too incomplete to allow an agent to use this tool effectively without external knowledge.

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 two parameters ('message' and 'inputs') have only generic placeholder descriptions. There is no explanation of what content they expect, how they affect the list_owners action, or what formats are acceptable. The schema provides no additional detail.

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 the specific action 'list_owners' and implies it lists HubSpot owners, but it does not explain what owners are or what the action actually does. It relies heavily on the action name being self-explanatory, which may not be true for all users.

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?

The description provides no guidance on when to use this tool, how to construct the 'message' or 'inputs' fields, or what alternatives might be more appropriate. It is a generic wrappers that offers no usage context.

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