RunRule

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

No annotations are provided, and the description gives no behavioral information. There is no disclosure of side effects, permissions required, or what the invocation entails, leaving the agent completely in the dark about the tool's behavior.

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?

While very concise (2 words), the description is severely under-specified. Conciseness should not come at the cost of clarity; here it fails to communicate any useful information.

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 this is a rule execution tool with no output schema, no annotations, and no behavioral details, the description is completely inadequate. It lacks essential context for safe and correct invocation.

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?

The input schema is empty (0 parameters), and schema description coverage is 100%. Per guidelines, baseline is 3. The description adds no extra meaning, but the schema already conveys the lack of parameters, so it meets the minimum.

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 'Run rule' is a tautology that merely restates the name. It does not specify what the tool does, what kind of rule it runs, or what the result is, making it impossible for an agent to understand its purpose.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling tools related to rules (CreateRule, DeleteRule, EnableRule, RunRules), there is no way to distinguish when to use RunRule vs. RunRules or others.

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