tenki_delete_snapshot

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

Annotations already declare destructiveHint=true and readOnlyHint=false, which covers the safety profile. The description adds 'permanently' to emphasize irreversibility and 'by ID' to specify the targeting mechanism, but it doesn't disclose additional behaviors like whether the snapshot must be unattached or what happens if the ID is invalid. Given the annotations carry the main burden, a 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, front-loaded sentence: 'Permanently delete a snapshot by ID.' It contains no filler and immediately conveys the action, the object, and the key modifier (permanently) and targeting mechanism (by ID). 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 delete operation with one parameter and no output schema, the description is sufficiently complete. It covers what the tool does and the essential detail of deletion by ID. While it doesn't discuss error conditions or prerequisites, the annotations handle the destructive nature, and the tool's simplicity means an agent has enough information to call it 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?

The schema has a single required parameter snapshot_id with no description (0% coverage). The description's 'by ID' confirms that this parameter is the snapshot identifier, but it doesn't provide extra detail on format or provenance. While the parameter name is self-explanatory, the description adds only marginal value beyond the schema field name.

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 states the specific action (permanently delete) and resource (snapshot) and includes the key detail that deletion is by ID. It clearly distinguishes from sibling tools like tenki_get_snapshot, tenki_list_snapshots, tenki_create_snapshot, and tenki_update_snapshot, making the tool's 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 makes it obvious when to use this tool: when a snapshot needs to be permanently removed. It doesn't explicitly mention alternatives or exclusions, but the sibling list shows no other snapshot deletion tool, so the context is clear enough for an agent to select it appropriately.

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