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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful context that results are membership-scoped (i.e., tied to the authenticated user, no user parameter needed) and names the underlying endpoint. It says nothing about result size, pagination behavior beyond the schema field, or ordering.

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?

Three tight sentences, each earning its place: identity/scope first, workflow positioning second, endpoint reference last. Everything is front-loaded with zero padding.

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?

For a one-optional-parameter read tool with no output schema, the description covers purpose, scope, and its role as the source of organization_id for downstream calls. It does not describe the returned organization objects, but with annotations carrying the safety profile and only one documented parameter, the gap is minor.

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 description coverage is 100% and the single 'continuation' parameter is fully documented in the schema, so the description does not need to compensate. It adds nothing about the parameter, so the baseline 3 applies.

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 first sentence gives a specific verb ('List') and resource ('organizations') plus the scope ('you are a member of'), which no sibling tool shares — all other list_* tools cover events, attendees, orders, venues, discounts, ticket classes, or inventory tiers. It is impossible to confuse this with any sibling.

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?

'Almost every other tool needs an organization_id from here' is unusually strong routing guidance: it positions this as the prerequisite discovery call in the workflow. It stops short of explicit when-not-to-use or naming a specific alternative call, so it lands at 4 rather than 5.

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