pmg_ruledb_rules_list

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

No annotations are provided, so the description carries the full burden. It clarifies the operation is read-only and describes the return content (full hydrated rule list with fields). However, it does not disclose error conditions, rate limits, or authentication specifics beyond the config hint.

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?

The description is extremely concise: two sentences plus a path line. It front-loads the core purpose ('List all PMG RuleDB rules'), includes the read-only qualifier, path, and return details. Every sentence is essential.

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 presence of an output schema and the description stating what is returned (from/to/what/when/actions), the description is fairly complete. It lacks details on pagination, limits, or specific config requirements beyond the hint, but these are minor omissions for a list-all read operation.

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 proximo_target, and its schema description is detailed. The tool description adds no additional parameter information beyond referencing the config, so it provides no extra value.

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, specifies it is a read operation, and provides the PMGsh path. It distinguishes from sibling tools like pmg_ruledb_rule_get (single rule) and pmg_ruledb_digest.

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?

The description mentions the prerequisite 'Needs PROXIMO_PMG_* config' but does not explicitly state when to use this tool versus alternatives like pmg_ruledb_rule_get or pmg_ruledb_digest. Guidance is implied by sibling context but not explicit.

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