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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description still adds real context: membership and read-scope preconditions, the two supported credential paths (Bearer header or key argument), and a warning that clients may retain the key in task history. That last point goes beyond structured fields and is genuinely useful for safe invocation.

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?

Purpose is front-loaded in the first sentence and the auth note follows logically, but the key-retention security warning is repeated almost verbatim from the schema's 'key' description, which is redundant padding in an otherwise short block.

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 no output schema, the description carries the burden of indicating what is returned, and it does name the two returned elements (community metadata and the member's role). Preconditions and auth are also covered, leaving only the exact shape of the returned metadata unspecified.

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%, so both parameters are already documented in the schema. The description's auth explanation largely restates the 'key' property description rather than adding new syntax or constraints, so the baseline of 3 is appropriate.

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 states a specific verb and resource: read community metadata plus the authenticated member's role. It is clear what the tool returns, but it never distinguishes itself from close siblings such as 'communities', 'community_activity', or 'community_thread', so an agent cannot route with full confidence from the text alone.

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?

It supplies prerequisites (requires membership and read scope) which imply when the call will succeed, but gives no explicit when-to-use versus alternatives, no when-not guidance, and no pointer to sibling tools for related data.

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