Rules List

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

readOnlyHint already marks it read-only; the description reinforces this with 'list' and adds useful context about surfacing load rejections, with no hidden side effects indicated.

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?

Two short, focused sentences with the action and resource front-loaded; no unnecessary words or repetition.

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?

Adequately explains what the tool returns conceptually (loaded and rejected rules) and when to use it, but the parameter meanings are left unexplained and the output schema is not shown, so full context relies on external schema details.

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 schema has two optional parameters (kind, phase) with no descriptions, and the tool description never mentions them, providing zero guidance on their meaning or allowed values.

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?

Clearly states the verb 'list' and the resources 'loaded detection rules and plugins', and explicitly includes rejected rules. Distinguished from rules_reload/rule_test by focusing on enumeration of loaded state.

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?

Provides a concrete triggering scenario ('check this when a scan finds less than expected') but does not mention alternatives or when not to use the tool.

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