delete_webapp_deployment

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

The description uses 'safe deletion' but does not explain what safety entails (e.g., irreversible, confirmation required, or soft delete). With no annotations, the description carries the full burden but lacks crucial behavioral context for a destructive operation.

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 short phrase with an emoji, which is concise but under-informative. It front-loads the action but sacrifices necessary details, making it barely adequate.

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?

Given no output schema and no annotations, the description should explain the effect (e.g., permanent deletion), return value, or prerequisites. It covers none of these, leaving significant gaps for an agent to use the tool correctly.

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 coverage is 100%, so baseline is 3. The description adds no additional meaning beyond the schema's parameter descriptions. The tool name and schema already convey the parameter purposes adequately.

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 'Web アプリデプロイメントの安全削除' clearly indicates the action (delete) and resource (web app deployment). It distinguishes from sibling tools like deploy_webapp or update_webapp_deployment by explicitly naming the delete operation.

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 (e.g., smart_update_webapp). Prerequisites, such as needing the deployment ID from list_webapp_deployments, are not mentioned, and there are no exclusions or context given.

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