deleteResource

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds only the 'session-scoped' scope detail; it says nothing about behavior when resourceId does not exist, whether deletion is reversible, or how sessionId routing affects cleanup.

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 front-loaded sentence with the verb, cardinality, scope, and key parameter all in place. Nothing is wasted or buried.

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 one-required-parameter delete with an output schema present, the definition covers enough to call the tool correctly. The minor gap is the unexplained interaction between the optional sessionId routing and the session-scoped deletion.

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%, so both parameters are documented in the schema itself, giving a baseline of 3. The description restates resourceId's role but adds no format, constraint, or sessionId interaction detail beyond what the schema already says.

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?

Clear specific verb (Delete) plus resource (one session-scoped resource) and an identifier (resourceId). The 'session-scoped' qualifier meaningfully distinguishes it from sibling removers like removeLayer, removeEntity, and clearAll. It does not explicitly name a sibling, so it falls short of a 5.

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 states only what the tool does, never when to use it versus the obvious alternatives (storeResource, listResources, clearAll, removeEntity). No prerequisites, no conditions, no exclusions are provided.

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