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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds valuable context: requires login, splits results into two groups, does not include agreement text or answers, and notes the server-side expansion cost. No contradiction with annotations; adds meaning beyond them.

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?

Description is tightly structured into three labeled sections (purpose, composition chain, pitfalls). Every sentence earns its place: the main purpose is front-loaded, then routing guidance, then caveats. Zero fluff despite being informative.

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 list tool with no parameters and no output schema, the description covers everything an agent needs: what it returns, how to consume the returned IDs, and operational cautions. It even notes the server-side cost to prevent misuse. Nothing is missing.

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?

Tool has zero parameters, so baseline is 4. The description explains the output structure (two groups) and how to use the returned IDs, which is effectively the semantic payload of this tool. No schema coverage needed since there are no params.

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 ('list') and resource ('my organization memberships'), and clearly differentiates the two output groups (joined vs pending). The description distinguishes it from siblings like list_organization_members and list_my_organization_tasks by specifying exactly what this tool returns.

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?

Provides explicit when-to-use guidance: it tells the agent to use membershipId for update_my_organization_membership and id for list_organization_applications/list_my_organization_tasks. It also gives exclusions: don't call management tools on pending organizations (will 403) and warns against looping. This is far beyond typical guidance.

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