list_rules

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety and determinism profile is covered without prose. The description adds the field set, which is useful orientation, but says nothing about volume, ordering, or whether the list can be empty — gaps that matter for a zero-param list.

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 front-loaded sentence with the resource first and the field list after the colon. No filler, no restatement of the name.

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 an output schema present, the description need not document return structure, and a zero-param read tool carries little hidden complexity. What remains unstated — ordering, result volume, empty-list behavior — is minor but non-zero for an agent deciding whether to call this first.

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 no parameters, so there is no parameter semantics to explain; the baseline for a parameterless tool applies. The description's field enumeration is technically about return values rather than inputs, but nothing is missing on the input side.

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+resource ('List the reviewed advisory rules') and enumerates the fields returned (id, advisory, CVEs, title, exposure summary). It never names a sibling or clarifies scope versus list_devices, so differentiation is left to inference, but the purpose itself is unmistakable.

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?

Usage is only implied by the verb 'List' and the zero-parameter signature; there is no explicit when-to-use, no prerequisite, and no mention of alternatives like check or report. An agent can reasonably guess this is the enumeration entry point for rules, but the description does nothing to route it.

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