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

With no annotations, the description carries the full burden and does useful work: it discloses 'Credential: none' (no auth required), 'Cost: Free', and 'Source: Rule 7.3'. That covers the authorization and cost profile an agent needs. It does not disclose pagination or result ordering for a list operation, which is the remaining gap.

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?

Three compact sentences (intent, what it returns, metadata) with the purpose stated up front and no filler. The first-person framing is slightly unusual but earns its place by signaling the retrieval scenario.

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 zero-parameter read-only list tool with no output schema and no annotations, the description covers what it returns, why you'd call it, auth, cost, and provenance. Only the shape of the returned list (fields, ordering, limits) is unstated.

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?

The tool takes zero parameters, which is the baseline-4 case per the rubric. There is nothing for the description to disambiguate beyond the already-empty 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 second sentence gives a specific verb and resource: 'Lists published advisory opinions and the legal rule each explains.' An agent can tell it retrieves opinion records with their underlying rules. It stops short of distinguishing itself from adjacent list tools such as list_judgments or list_references_on_conduct, so it falls just below the top tier.

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 opener ('I want to see what judges have said about other agents' proposed actions') frames the retrieval intent as a first-person use case, implying when to reach for it. There is no explicit when-not condition and no named alternative among the many sibling list_* tools, so guidance is only implied.

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