pmg_action_objects_list

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

Starts with 'READ-ONLY', which is a key behavioral trait. Describes return format as list of dicts with 'editable' flag and explains that non-editable items are built-ins and cannot be modified. No annotations were provided, so description carries the full burden. Minor omission: no mention of error behavior if config is missing.

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 paragraphs, front-loaded with key information (read-only, list all, config requirement, sibling relationship). Every sentence is valuable, no fluff.

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 that output schema exists, description doesn't need to detail return values. It covers read-only, config need, sibling differentiation, and result structure. Missing a note about no filtering capability, but overall adequate for a list tool.

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% and description adds no additional meaning beyond the schema for the sole parameter (proximo_target). Baseline of 3 is appropriate.

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?

Description clearly states 'READ-ONLY: list all PMG RuleDB action objects', specifying verb and resource. It also distinguishes from sibling `pmg_ruledb_rule_actions_list` by noting that tool is for one rule's attached actions.

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?

Explicitly states prerequisite: 'Needs PROXIMO_PMG_* config.' Provides alternative: 'For one rule's attached actions use pmg_ruledb_rule_actions_list instead.' This gives clear when-to-use and when-not-to-use guidance.

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