deleteRule

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

No annotations are present, so the description must fully disclose behavioral traits. It only states 'Delete rule(s).' which indicates mutation but offers no details about reversibility, cascading effects, permissions, or the consequences of deletion.

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 extremely concise at two words, which is efficient but may be too brief. It lacks structure and does not include any additional context. It earns a 3 as it is minimal but not wasteful.

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 the simple input schema (one integer parameter) and no output schema, the description still fails to provide necessary context about what happens when a rule is deleted, such as effects on associated data or required permissions. It is incomplete for an agent to safely invoke.

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% for the single parameter 'id', which is described as 'Id of rule'. The description adds no additional meaning beyond the schema. Given full coverage, the baseline is 3, and the description does not provide extra semantic information.

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 'Delete rule(s).' clearly states the action and resource, and it distinguishes from sibling tools like deleteClient or deleteColumn by naming the specific entity. However, it does not specify whether it deletes a single rule or multiple rules, which the input schema indicates is a single id.

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 explicit usage guidelines are provided. The resource name 'rule' implies when to use this tool (when you need to delete a rule), but there is no discussion of alternatives or when not to use it. The sibling tools cover other entities, so the intended use is implied.

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