delete_rule

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

Annotations provide no destructive hint, so the description carries the full burden. 'Permanently delete' explicitly discloses irreversibility, which is key for a mutation tool. However, it does not mention permissions, side effects, or what happens to dependent data, leaving some gaps.

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 sentence of nine words, front-loaded with the verb and resource. No filler or redundancy; every word contributes.

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 tool with an output schema, the description covers the core action and permanence. However, it lacks usage guidelines and any notes about alternatives or side effects, making it adequate but not complete.

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 description coverage is 100% with both parameters described as 'Rule UUID' and 'Portfolio UUID'. The description adds no extra meaning beyond tying the rule to a portfolio, so 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 clearly states the verb 'delete', the specific resource 'systematic trading rule', and the context 'from a portfolio'. This distinguishes it from siblings like toggle_rule (which likely enables/disables) and update_rule (which modifies).

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 compared to alternatives. Since siblings include toggle_rule and update_rule, the description could have mentioned that this is for permanent removal, while toggle_rule is for temporary deactivation, but no such context is given.

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