arvan_delete_cdn_app

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

The description only states the action 'Delete', which is consistent with the destructiveHint annotation. It adds no additional behavioral context beyond what annotations already provide, such as reversibility, permissions, or side effects.

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, concise sentence with no redundant information. It could be slightly expanded to include parameter context, but it remains appropriately brief.

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 operation with two required parameters and no output schema, the description is minimally adequate. However, it lacks details on how to obtain the app_id or domain, and any potential consequences, which would make it more complete.

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?

With 0% schema description coverage, the description fails to explain the meaning or source of the two required parameters. Mentioning 'by id' only hints at app_id, leaving domain completely unexplained, which is insufficient for correct invocation.

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 the resource (CDN app), and mentions identification 'by id', which aligns with the app_id parameter. However, it fails to mention the required domain parameter, making it slightly incomplete.

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 is provided on when to use this tool versus alternatives like other delete tools (e.g., arvan_delete_dns_record). There are no prerequisites or contextual hints for appropriate usage.

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