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

Annotations already declare readOnly/idempotent/non-destructive, so the safety bar is covered. The description adds genuinely useful context the annotations cannot: 'Free; no model runs' (cost/latency) and that the catalogue is 'live' with a version, plus the caveat that the rule count is whatever the live catalogue says. No return format details, but this is modest added value over structured data.

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?

Front-loaded with the key directive, then a single dense enumerative paragraph. The catalogue listing is long but each item (criteria, weight, gate role, thresholds, bands) is informative rather than filler.

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 must carry the return shape, and it does: it names the per-rule fields and the arithmetic block (status scores, thresholds, bands, gate, toggleable policy contexts). That is close to complete for a parameterless read; only the concrete data types/format of those values are left implicit.

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?

Zero parameters, so the baseline is 4; the description correctly makes no parameter claims and instead spends its budget on the return payload.

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?

States a specific verb and resource ('Read the bar' / returns the live catalogue with version) and enumerates exactly what the catalogue contains (ids, criteria, weights, gates, arithmetic). An agent can tell this is the rule-catalogue read, though it does not explicitly contrast itself with bar_status or get_brief_template.

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?

'Read the bar before judging anything' gives a clear sequencing cue that this is the entry point to call first. It stops short of naming alternatives or exclusions, so the agent must infer why it would choose this over the sibling bar_status.

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