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

Annotations already declare readOnly=true, idempotent=true, destructive=false, so 'Read-only, free' partly restates structured data; 'free' (no cost) is the only net-new behavioral fact. The paging behavior (offset/next_offset) is disclosed but largely mirrors the offset schema description. Modest added context.

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?

A single dense sentence that front-loads the purpose and packs return fields, defaults, paging, and cost without wasted words. The clause chain with colons and semicolons reads slightly run-on, but it is information-dense rather than verbose.

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 usefully enumerates the returned fields (identifier, severity, family, title, documentation page) and covers defaults, filtering, and paging. Nothing essential for a read-only list tool is missing.

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 67% (above the 50% floor), and the schema already documents set, layer, family, and offset. The description reinforces 'filtered by layer, family or severity' but adds no syntax, format, or meaning beyond what the schema provides.

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 states a specific verb and resource ('The validation rules Ironfang Finance runs') and enumerates the returned fields, so an agent knows exactly what it produces. It does not explicitly distinguish itself from the sibling finance.rule.get (single-rule fetch), leaving that differentiation to inference.

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 useful selection guidance for the 'set' parameter (default = reviewed explanations; set=official = every pinned-artefact rule), which is genuine when-to-use info. However, it never explains when to reach for this tool versus finance.rule.get or ruleset.list, and there are no exclusions.

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