hubspot_list_owners

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

No annotations are provided, so the description carries the full burden. It does not disclose behavioral traits such as pagination (though schema has 'after' and 'limit') or rate limits. It is concise but lacks explicit details on behavior beyond listing.

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 extremely concise with two sentences. The first sentence states the main action, and the second provides the primary use case. No unnecessary words.

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?

Given there are 4 optional parameters, 100% schema coverage, and no output schema, the description adequately covers what the tool does and why to use it. It could mention pagination behavior briefly, but is otherwise complete for its simplicity.

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 coverage is 100%, so baseline is 3. The description does not add any meaning beyond the schema; it does not explain parameter details or provide usage examples.

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 clearly states the tool lists all HubSpot owners (users) and explicitly mentions the use case of finding owner IDs for assigning to contacts, companies, deals, or tickets. It distinguishes from sibling tools like hubspot_get_owner by implying this is for listing all owners, not a single one.

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 explicitly states when to use: to find owner IDs for assignment. It does not explicitly state when not to use or mention alternatives, but the context of sibling tools (e.g., hubspot_get_owner) suggests that for a specific owner, one would use that tool instead.

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