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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and repeatability are covered. The description adds useful behavioral detail about what the output contains, namely per-address ages and same-day creation pattern flags. It does not mention external lookups implied by openWorldHint, coverage limits, or what happens for agents with no reviewers.

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 short sentences, front-loaded with the core question and then the return content. Nothing is padded, though the rhetorical question form is slightly less efficient than a direct statement.

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 appropriately states what is returned (address ages and pattern flags). For a two-parameter read-only analysis tool this is largely sufficient, though the shape of the returned data and handling of empty reviewer sets remain 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 coverage is 100%, with id and chain already documented as 'Agent ID' and 'Chain slug'. The description adds no additional meaning about these parameters, so the baseline of 3 applies.

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 resource and verb: it returns reviewer addresses and their ages for an agent, plus pattern flags. An agent can distinguish it from siblings like reviewer_wallet or address_age. It is slightly ambiguous about whether reviewer identities themselves are returned or only address ages, which keeps it from a 5.

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?

There is no explicit when-to-use guidance, no prerequisites, and no routing to alternatives such as address_age (single address) or reviewer_wallet (reviewer wallet data). The agent must infer that this is the batch reviewer-level analysis from the wording alone.

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