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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds one genuinely useful behavioral fact beyond that — an authentication/key requirement — but says nothing about result shape, pagination, or what happens with no identity.

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 text is short but broken: it trails off with an ellipsis and then appends a second fragment ('Needs key or sign-in'), so it reads as two incomplete sentences rather than a front-loaded summary. Brevity here reflects truncation, not discipline.

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 carries the full burden of explaining the return shape — and because it is truncated, the enumeration of returned data (role, rights, scope derivations) is cut off exactly where detail was needed. An agent cannot tell what the payload looks like before calling.

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?

One optional parameter ('key') with 0% schema description coverage, so the description must compensate; 'Needs key or sign-in' does at least imply that the key parameter is an auth credential and that there is a sign-in fallback when it is omitted. That is meaningful but minimal — no format, no source of the key, no behavior when an invalid key is supplied.

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 description names the resources returned (workspaces, groups, scopes, role, rights) which identifies this as a 'my memberships' retrieval tool, but there is no verb and the text is truncated mid-clause ('directly or through a...'), so the scope of what is returned is left unresolved. It is distinguishable from siblings like spaces_browse in spirit, but not sharply.

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?

No explicit when-to-use statement and no named alternatives (spaces_browse, groups_mine, orgs_mine, orgs_mine-style siblings all overlap). The only guidance is the trailing 'Needs key or sign-in', which is a prerequisite hint rather than a usage rule.

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