delete-rum-retention-filter

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Delete' but does not explain consequences (e.g., irreversible, propagation delays) or authentication requirements. The description adds minimal context beyond the verb.

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 six words, containing no filler or redundant information. It is perfectly concise and front-loaded, meeting the efficiency standard.

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 delete tool with no output schema, the description lacks crucial details such as return value (e.g., success message or deleted object), side effects, and irreversibility. Given the simplicity, more context is needed for an agent to use it correctly.

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 appId and filterId adequately described in the schema. The tool description adds no additional meaning or context for the parameters, so it meets the baseline but does not improve upon 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 'Delete a RUM retention filter by ID' clearly states the action (delete) and resource (RUM retention filter), distinguishing it from siblings like create, update, and list. However, it does not mention that the appId parameter is also required, which is a minor omission.

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 no guidance on when to use this tool versus alternatives (e.g., delete-rum-metric) or what prerequisites are needed (e.g., having the correct appId). No when-not-to-use or alternative suggestions are given, making it hard for an agent to decide when to invoke this.

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