deleteBusinessRules

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

No annotations are provided, and the description does not disclose any behavioral traits such as whether deletion is irreversible, if it affects dependent rules, or required permissions. The minimal description offers no behavioral insight beyond the action.

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 short (just the name and one parameter note). While not verbose, it lacks structure and does not provide a complete sentence describing the tool's function. It feels under-specified rather than 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?

With no output schema and a simple deletion operation, the description should at least mention that the tool deletes a specific rule or what happens upon success/failure. It does not address return values, error states, or any contextual behavior, making it incomplete.

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 has 100% coverage with descriptions for all three parameters (host, apiKey, businessRuleId). The description only restates the businessRuleId parameter, adding no new meaning. Baseline is 3 since the schema already documents parameters well.

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 tool's name 'deleteBusinessRules' clearly indicates it deletes business rules. The description repeats the parameter for the rule ID, which reinforces the purpose, but does not explicitly state the action or distinguish it from sibling tools beyond the verb. The purpose is clear from context.

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 like updateBusinessRules or addBusinessRules. There is no mention of prerequisites, such as needing to list rules first or confirmation steps.

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