Simulate ERDL Rule

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

Description implies it is a safe, non-destructive simulation ('test... BEFORE creating'), but without annotations it does not explicitly state it is read-only or has no side effects. Additional statements about safety would improve transparency.

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 with front-loaded purpose and clear flow. Efficient and easy to parse, though it could be slightly more concise.

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?

Covers the essential workflow: test before creation, show results, ask to proceed. However, it does not explain what the '3 scenarios' are or how they are generated, leaving minor ambiguity for the agent.

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 the description does not add extra meaning beyond what is already in the parameter descriptions. Baseline 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?

The description specifies 'Test a potential rule against 3 scenarios BEFORE creating it,' providing a specific verb ('test'), resource ('rule'), and scope ('before creation'). This clearly differentiates it from the sibling tool erdl_create_rule.

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 instructions: 'Always call this BEFORE erdl_create_rule when the user says "remember this" or "create a rule".' It also tells the agent to show results and ask for confirmation, leaving no ambiguity about when and how to use the tool.

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