pmg_ruledb_rule_from_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 explicitly declares 'READ-ONLY', which informs about safety. It states the return type ('list of object dicts') and the need for PROXIMO_PMG_* config. This level of transparency is good for a read operation.

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 concise: two short paragraphs. The first sentence immediately states the core purpose. No superfluous words. It efficiently conveys purpose, requirements, and related tools.

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?

Combined with the input schema (100% coverage) and existence of an output schema, the description is complete. It covers what the tool does, what it returns, and how to obtain the required id. It also points to related tools for other rule components, making it self-contained within the sibling set.

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 is 3. The description adds context: id_ is 'rule ID (e.g. '100') from pmg_ruledb_rules_list', linking to another tool. This clarifies the source of the id. For proximo_target, the description mostly mirrors the schema. Overall, it adds value 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 the tool lists 'from' objects attached to a PMG RuleDB rule. It uses the verb 'list' and specifies the resource ('from' objects of a rule). It distinguishes from sibling tools like pmg_ruledb_rule_to_list and mentions counterparts for what/when/actions, making the purpose specific and unambiguous.

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 explicitly points to alternatives: 'Use pmg_ruledb_rule_to_list for the 'to' side, and the what/when/actions counterparts for the rest.' It also mentions a prerequisite (PROXIMO_PMG_* config). While it doesn't explicitly state when NOT to use it, the guidance is clear enough for selection.

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