delete-rum-application

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

The description implies a destructive mutation ('Delete') but provides no details on irreversibility, cascading effects, authentication requirements, or error handling. Without annotations, the agent cannot assess risks beyond the basic 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?

A single sentence of 6 words conveys the core action with no superfluous information. Every word is necessary and the structure is efficient.

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 delete with one parameter, the description is functional but incomplete. It omits expectations for return values, error states, and safety implications (e.g., is deletion immediate? reversible?). No output schema exists to compensate.

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% and the only parameter 'id' is already described in the schema. The description adds no additional meaning beyond what the schema provides, meeting the baseline of 3.

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 (RUM application) and identifier method (by ID). It is specific and distinct from sibling delete tools by resource type, though it lacks any nuance about scope or effects.

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 on when to use this tool versus alternatives like 'get-rum-application' or 'list-rum-applications'. No mention of prerequisites, confirmation, or irreversible nature, leaving the agent without decision context.

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