hubspot_list_owners

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

With no annotations provided, the description carries the behavioral disclosure burden. It clearly marks the operation as READ-ONLY, which is a key safety trait, and specifies that it operates on a chosen portal. It does not detail output shape or edge cases, but for a simple list operation this is acceptable.

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 two short sentences that front-load the action and purpose, then add the read-only safety note. Every word adds value, with no redundant or filler content.

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 the tool's simplicity, one required parameter, and no output schema, the description provides enough context for an agent to invoke it correctly: it states what is listed, why it might be used, and that it is read-only. A brief note about return format would make it fully complete, but it is not a major gap.

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% and the single required parameter 'instance' already has a clear description explaining which portal to use and the setup command. The tool description adds only the phrase 'chosen portal', which adds minimal meaning beyond the schema.

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 uses a specific verb ('List') and a specific resource ('CRM owners (users)') and adds the intended use case ('to resolve owner ids to people'). This clearly distinguishes it from sibling tools like hubspot_list_objects and hubspot_list_instances.

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 clear context for when this tool is useful: when you need to resolve owner ids to people. It does not explicitly name alternatives or exclusions, but the purpose statement is enough to route an agent toward this tool for owner-related lookups.

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