Api assets destroy

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

Annotations declare destructiveHint=true and readOnlyHint=false, but the description describes a view/edit endpoint and never mentions deletion, irreversibility, or required caution. This directly contradicts the destructive behavior signaled by the annotations.

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 short and not bloated, but its only sentence is generic boilerplate that does not earn its place. Brevity does not help when the content is misleading.

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 destructive one-parameter tool with no output schema, the description should at minimum state that it deletes an asset by ID. Instead it omits the deletion entirely and gives an inaccurate view/edit summary, leaving the agent without essential context.

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 single required parameter 'id' has 0% schema description coverage, and the description adds no information about what the ID identifies or how it is used. The description does not compensate for the missing parameter documentation.

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 says the endpoint allows assets to be 'viewed or edited', but the tool is explicitly a destroy/delete operation. It neither states the actual verb (delete/destroy) nor distinguishes this tool from sibling update or retrieve tools.

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?

There is no guidance on when to delete an asset, when not to, or what alternatives exist. Worse, the description implies viewing/editing rather than deletion, which could lead an agent to misuse it.

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