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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds no behavioral context beyond that—no mention of pagination, limits, or what happens with missing roles. Given the strong annotation coverage, this is acceptable but adds no extra transparency value.

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 description is a single, terse sentence that conveys the essential purpose with no filler. It front-loads the key information about members and roles, and every word contributes to clarity. This is an example of appropriately minimal specification.

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 simple two-parameter tool with an output schema, the description covers the core purpose but omits usage guidance and any context about return behavior or limitations. Given the annotations and schema, it is minimally adequate but leaves the agent without explicit instructions on when to use it or what to expect beyond the schema.

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 coverage is 50%: 'role' has a description, 'slug' does not. The description implies 'slug' refers to the collective identifier by saying 'for a collective', which adds slight meaning. However, the description does not explicitly document 'slug' format or semantics, and the role values are already enumerated in the schema. It offers marginal value beyond the 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 description clearly states the tool returns members of a collective, listing the role types (backers/sponsors/admins/contributors). It is specific about the resource (members of a collective) and the verb is implied (list/get). It does not explicitly distinguish from sibling tools like 'collective', but the purpose is unambiguous.

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 description provides no guidance on when to use this tool versus alternatives such as 'collective' or 'entity_profile'. There are no explicit conditions, exclusions, or prerequisites mentioned. An agent would have to infer usage from the description alone, which lacks any contextual guidance.

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