pmg_ruledb_rule_actions_list

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

Discloses read-only nature and explains why it reads from /config instead of the dedicated endpoint. Without annotations, this description adequately covers key behavioral traits for a 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?

The description is brief, front-loaded with 'READ-ONLY', and structured with a note and clear parameter guidance. Every sentence provides value without 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?

Given 2 parameters and presence of output schema, the description covers purpose, behavior, and simple usage. Could mention error cases like nonexistent rule ID, but overall sufficient.

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%, so baseline 3. Description adds value by providing an example and source for id_, clarifying its origin. Doesn't elaborate on proximo_target, but schema covers it.

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 'actions' objects attached to a PMG RuleDB rule, using specific verb 'list' and resource 'rule actions'. It distinguishes from siblings like pmg_ruledb_rule_get and pmg_ruledb_rule_action_attach.

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 clear context for usage, including the workaround for a 501 error and prerequisite that id_ comes from pmg_ruledb_rules_list. Does not explicitly state when not to use it, but implies it's for reading actions only.

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