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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds the non-obvious authorization constraint (owners/admins only) and discloses that the response bundles two datasets — org members and the assignable seller/store ids — which is genuine context beyond the annotations.

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?

A single front-loaded sentence with no filler; every clause names a returned field. The nested parenthetical runs long, but the information is dense and earns its space.

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, so the description must carry the return shape — and it does, listing each member attribute plus the separate seller/store id collections. What is missing is whether results are paginated, ordered, or scoped across multiple clients, which matters for an org-level listing.

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 tool takes zero parameters, so the baseline of 4 applies. The description correctly implies no input is needed and spends its budget explaining the payload instead.

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?

States a specific verb and resource (list the people of the user's Vendooly organization) and enumerates exactly what is returned: role, status, assigned sellers and WooCommerce stores, per-function permissions, plus assignable seller ids and store ids. It is clearly distinct from write siblings like invite_team_member, though it never names a sibling explicitly.

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 clause 'Owners/admins only' gives a real access prerequisite, which is more than most list tools offer. However there is no explicit when-to-use route (e.g. 'call this before invite_team_member to see existing members') and no stated alternative or exclusion.

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