Delete Artifact

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

Annotations already disclose destructiveHint=true and readOnlyHint=false. The description adds 'permanently' to emphasize irreversibility and 'scoped to a user and session' to highlight required context, providing value beyond the annotations. It does not mention error outcomes, but the annotation coverage makes this acceptable.

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 that front-loads the action ('Permanently delete') followed by the resource and scope. It contains zero filler words and is appropriately concise for the tool's simplicity.

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?

This is a simple delete operation with three well-documented parameters and no output schema. The description, combined with annotations, covers the essential aspects: permanence, scoping, and destructive nature. It could mention return values or not-found behavior, but these are not critical for a delete tool.

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 the baseline is 3. The description adds minimal detail beyond the schema, only reinforcing that deletion is by id and scoped to user/session. It does not introduce any new parameter-specific semantics.

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 uses the specific verb 'permanently delete' and identifies the resource as 'an artifact by id', which clearly distinguishes it from sibling tools like get, update, or list artifacts. It also adds scoping to a user and session, making the purpose unambiguous.

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 clear context for when to use this tool: whenever an artifact must be permanently removed. It does not explicitly name alternatives or exclusions, but the delete operation is self-evident and the scoping to user/session clarifies applicability.

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