delete_security_monitoring_rule

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a deletion operation, implying it's destructive, but doesn't mention whether deletions are permanent, reversible, require confirmation, or have side effects. It also doesn't address authentication needs, rate limits, or error conditions. The single constraint about default rules is helpful but insufficient for a mutation tool.

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 (two short sentences) and front-loaded with the core purpose. Every word earns its place: the first sentence states the action, and the second adds a critical constraint. There's no redundancy or unnecessary elaboration.

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 deletion tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after deletion (e.g., confirmation message, error if rule doesn't exist), what 'default rules' means, or how to identify them. Given the destructive nature and lack of structured safety hints, more behavioral context is needed for safe usage.

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 tool has 0 parameters, and schema description coverage is 100%. The description doesn't need to explain parameters, and it appropriately doesn't mention any. The baseline for 0 parameters with full schema coverage is 4, as there's no parameter information to add beyond what's already documented in 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 action ('Delete') and resource ('an existing rule'), which is specific and unambiguous. However, it doesn't distinguish this from sibling tools like 'delete_security_monitoring_cloud_workload_security_agent_rule' or 'delete_security_monitoring_configuration_security_filter', which also delete security-related rules but for different rule types.

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 provides one important usage constraint: 'Default rules cannot be deleted.' This gives some guidance on when NOT to use the tool. However, it doesn't specify when TO use it versus alternatives (like update operations) or mention any prerequisites (e.g., needing rule IDs or specific permissions).

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