Delete Asset

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description adds the important nuance of permanence with 'Permanently delete'. However, it does not disclose other behavioral details such as side effects, error behavior when the asset does not exist, or authorization requirements. Given the strong annotation coverage, a score of 3 is appropriate.

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 with no filler, efficiently conveying the action, resource, and permanence. Every word earns its place.

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-parameter delete tool with strong annotations and schema coverage, the description is largely complete. It communicates the essential permanence aspect. It does not explain return values or failure behavior, but these are not required given the tool's simplicity and lack of an output schema.

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 input schema provides 100% coverage for the only parameter, asset_id, with an 'Asset id' description. The tool description's 'by id' simply echoes the parameter, adding no new meaning beyond what the schema already conveys. Baseline 3 applies due to high schema coverage.

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 'Permanently delete an asset by id' clearly states the action (delete), resource (asset), and method (by id). It distinguishes this tool from sibling delete tools for other entity types (e.g., agents, contexts).

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 context is clear: use this tool to permanently remove an asset by its id. There are no alternative delete-asset tools among siblings, so explicit alternative guidance is less critical. It does not mention prerequisites or when not to use, but for a simple delete operation the context is sufficient.

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