list_organizations

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

With no annotations, the description carries the full burden and does so well: it discloses the auth requirement (Bearer PERSONAL_OAUTH_TOKEN) and a critical gotcha that organization_id differs from organizer_id in an Organizer Profile URL. It does not describe pagination mechanics or rate limits, but the safety and identity context is well covered.

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 definition is long but deliberately sectioned (ENDPOINT, object fields, USE CASES, RESPONSE, AUTHENTICATION) and front-loads purpose before detail. Some content, such as the vertical enum listing, is arguably more than a list tool needs, but nothing is disorganized or buried.

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 no-parameter, no-output-schema list tool, the description supplies everything needed: the endpoint, authentication requirement, a disambiguation caveat, the returned fields, and pagination presence. An agent has no unanswered questions required to invoke it correctly.

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 goes further by documenting the Organization object fields returned (id, name, image_id, vertical), which compensates for the absence of an output 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 opening sentence states a specific verb (List) and resource (organizations) with a precise scope constraint (the authenticated user is a member of), which cleanly separates it from get_organization and list_organization_members. An agent can distinguish this from all siblings without opening a schema.

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 USE CASES block gives concrete reasons to call it (obtaining organization_id for event creation, listing org events, managing members), which is strong positive guidance. It does not, however, name alternatives or exclusions (e.g., when to use get_organization or get_current_user instead), so it stops short of a full when/when-not.

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