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

Annotations already indicate this is a read-only, non-destructive operation. The description adds useful behavior beyond annotations by specifying the returned array structure and the empty-array case when no profiles exist.

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?

Two sentences, front-loaded with the purpose and followed by the return behavior. Every sentence earns its place by clarifying output shape and the empty-result case.

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 helpfully lists the return object fields and the empty-array case. It is complete enough for an agent to call and interpret the response, though it omits ordering or pagination details.

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 the single address parameter is already fully documented in the schema. The description adds only that profiles are looked up for that address across roles, which is meaningful but does not go beyond the baseline when the schema does the heavy lifting.

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 uses a specific verb+resource: 'List all contributor profiles for an address across roles.' It clearly states what the tool returns, though it does not explicitly differentiate from the related sibling pcc_contributor_register.

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 usage is implied: use this to retrieve contributor profiles for a given address. However, there is no explicit when-to-use or when-not-to-use guidance, and no alternative such as pcc_contributor_register is named.

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