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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered upstream. The description adds useful disclosure of what comes back (membership plus role: owner, admin, member), but says nothing about ordering, result size, or behavior when the user belongs to a single organization.

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?

Two sentences, front-loaded with the operation and scope, then the usage guidance. No filler or restatement of the title.

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?

With zero parameters and no output schema, the description still conveys the shape of the result (organizations plus the caller's role), which is the main thing an agent needs. It leaves minor gaps around ordering and pagination, but nothing that would block a correct call.

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 no parameters and schema coverage is 100%, so there is nothing for the description to disambiguate. Baseline applies; the mention of the 'role' field is a small extra since no output schema exists.

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 ('Lists organizations') plus the scope constraint ('the authenticated user is a member of') and the returned field (role). It does not explicitly contrast with the adjacent list_workspaces / list_workspace_people siblings, which an agent might confuse for the same hierarchy level.

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?

Gives two concrete situations to invoke it: choosing which organization to operate on, and answering questions about team membership. It stops short of exclusions or pointing at alternatives such as list_workspaces when the caller actually needs workspaces.

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