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

With no annotations, the description carries the burden, and it discloses that there is no input, where the data comes from, and the return shape (tagline, URL, and rules with rule/title/part). It does not mention error/ordering/freshness behavior, but this is a simple zero-input read tool.

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 compact two-sentence definition that front-loads the resource and use case, then gives output and alternative in the same breath. Every clause earns its place.

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-input list operation with an output schema, the description supplies purpose, usage trigger, output fields, and the relevant sibling. There is no meaningful missing context for correct invocation.

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?

There are zero parameters and 100% schema coverage, so the baseline is 4. The description adds 'No input', which confirms there is nothing more for an agent to supply.

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 identifies the resource ('the rules the model is held to, from the CONVENTIONS.md') and the exact use case ('resolve a rule number that a schema or a refusal cites, such as R9'). It also distinguishes itself from describe_rule by noting that describe_rule gives one rule's text.

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?

It gives a clear trigger for use ('rule number a schema or refusal cites') and names the sibling alternative describe_rule for the full text of one rule. It does not explicitly state when not to use list_rules, but the context is sufficient.

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