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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the useful fact that the lookup accepts either a Compoid ID or an OAI, but says nothing about auth requirements, behavior when the ID is not found, or result volume.

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?

A single sentence with zero filler, leading with the verb and resource and closing with the identifier constraint. Nothing is redundant or front-loaded poorly.

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?

An output schema exists, so return values need not be described, and the tool is a simple one-parameter lookup. The remaining gap is minor: no failure behavior or guidance on obtaining a valid ID when the agent does not already have one.

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 0%, so the schema alone gives no meaning for community_id; the description partially compensates by stating it accepts a Compoid ID or an OAI. It still omits format examples, whether slugs are accepted, and whether OAI is an alias for the same field.

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 a specific verb (Get) and resource (detailed information about a community) and states the lookup key (Compoid ID or OAI). This clearly separates it from search_communities, but it never names the sibling explicitly, so sibling differentiation is implied rather than stated.

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?

Usage is implied: retrieve the details of one known community when you already have its ID or OAI. There is no explicit when-to-use vs. when-not guidance and no routing to alternatives such as Compoid_search_communities for finding an identifier, Compoid_get_record_details for records, or Compoid_update_community for mutation.

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