delete_business_rule

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

With no annotations, the description carries the behavioral transparency burden. It discloses that deletion is permanent, which is critical for a destructive operation. However, it does not mention other relevant behaviors such as error conditions (e.g., if the rule is locked or missing), permissions, or cascading effects on the parent rule set. The 'permanently' qualifier adds value but leaves several behavioral aspects unaddressed.

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 a single, well-structured sentence that front-loads the verb and resource. There is zero wasted text—every word earns its place, including the important 'permanently' qualifier.

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?

For a simple two-parameter delete operation with an output schema present and full schema description coverage, the description is nearly sufficient. It conveys the core function and permanence. It could be more complete by mentioning what happens to associated data or any prerequisites, but given the simplicity and the schema's detail, it is adequately contextual.

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 provides 100% coverage with clear descriptions for both required parameters: rule_id and ruleset_id, including a clarifying note that ruleset_id is a UUID, not a name. The tool description adds no additional parameter information, so the schema alone is sufficient. Baseline of 3 is appropriate because the description does not enhance or contradict 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's function: 'Permanently delete a rule from a SAS Business Rules rule set.' The verb 'delete' and resource 'rule from a SAS Business Rules rule set' are specific, and the permanence qualifier distinguishes it from any soft-delete alternative. It also differentiates from sibling tools like delete_business_ruleset (which targets a rule set) and update_business_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?

The description implies usage—removing a specific rule from a rule set—but provides no explicit guidance on when to use it compared to alternatives, such as delete_business_ruleset or update_business_rule. The context is clear, but no exclusions or alternative references are mentioned, so the agent must infer from the tool name and schema.

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