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

No annotations are present, so the description carries full burden. It discloses that the data is wrapped in a proof envelope and includes a specific field, which is useful behavioral context. However, it does not mention potential caveats like pagination, response size, or access requirements, though the 'Return' wording implies a read-only operation.

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 exceptionally concise: two sentences with no filler. Key information (what is returned, the specific field, the proof envelope) is front-loaded and every sentence adds value.

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?

Given the tool has no parameters, no output schema, and is a straightforward list endpoint, the description provides sufficient context about the returned data and its envelope. The absence of explicit return format documentation is mitigated by the description's clarity about the payload contents.

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?

This tool has zero parameters, so the description does not need to explain input semantics. Per the rubric, a baseline of 4 is appropriate since there are no params to document, and the description adds clarity about the output contents.

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's action ('Return') and resource ('every rwa_family row' with 'attributed pool count'). It specifies a unique output field, dispute_contact_url, and differentiates from sibling tools like get_rwa_pools by focusing on rwa_families.

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 implies this tool is used when you need the complete list of rwa_family rows with their pool counts and the dispute contact URL. No explicit guidance on when not to use it or alternatives is given, but the purpose is self-evident within the context of sibling read tools.

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