pmg_ruledb_rules_list

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

Declares READ-ONLY, describes return format (hydrated rule list as dicts with fields). Could mention potential scale/performance implications but otherwise thorough for a read-only list tool.

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?

Three sentences: first gives purpose and config requirement, second describes return, third provides alternatives. Front-loaded and no extraneous information.

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?

Given the simple tool (list with one optional param) and output schema present, the description covers usage context, alternatives, return format, and prerequisites. Fully complete.

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 100% for the single parameter. The description adds context about needing PROXIMO_PMG_* config, which relates to the parameter's role. This provides useful guidance beyond the schema.

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 clearly states it lists all PMG RuleDB rules (hydrated rule list). It distinguishes from siblings by mentioning pmg_ruledb_rule_get for one rule and pmg_ruledb_digest for drift detection.

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-to-use: listing all rules; when-not: for a single rule use pmg_ruledb_rule_get, for drift detection use pmg_ruledb_digest. Also notes config requirement.

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