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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds value beyond that: 'Fails: nothing to refuse. Works with no key.' tells the agent there are no auth requirements or failure modes, which is not in the structured data. Minor gap only on caching/freshness of the rulebook.

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?

Labeled lines (When / Instead / Inputs / Returns / Fails) are front-loaded and scannable, with no wasted prose. The 'Returns' line mildly restates the opening sentence's field list, a small redundancy.

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?

No output schema exists, and the description compensates by enumerating the returned fields (id, title, stage, weight, fix). Inputs, failure behavior, auth requirements, and sibling alternatives are all covered, leaving nothing an agent needs in order to call it correctly.

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-parameter tool, so the baseline is 4; the description's explicit 'Inputs: none.' confirms the empty schema rather than adding semantics beyond it. Nothing more could reasonably be said about zero parameters.

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 (lists) and resource (the rulebook / every rule clickd checks) plus the exact fields returned. The sibling contrast lines make it distinguishable from clickd_brief and clickd_pages without opening any schema.

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?

Explicit 'When:' clause names two concrete situations (explaining a fix to a person, finding a rule's id), and the 'Instead:' clause routes to clickd_brief and clickd_pages with the exact condition that selects each. Nothing is left to inference.

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