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

Annotations already flag destructiveHint=true, but the description adds crucial context: 'ALL objects in the bucket are deleted' and the precondition of detachment. This goes beyond annotations by detailing scope of destruction and dependency requirement, which is essential 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?

Three short sentences, front-loaded with the primary action, then critical preconditions and consequences. Every sentence earns its place with no waste.

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 the tool's destructive nature, no output schema, and simple parameter, the description covers all necessary context: what it does, when it can be called (after detachment), and the full impact (all objects deleted). Nothing an agent needs to invoke it safely is missing.

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 and a single required parameter (bucketId), the description doesn't elaborate on the parameter's format or source. However, for a simple ID parameter on a delete tool, the lack of additional semantics is acceptable; the baseline for 0 params is 4, but here it's 1 param, so the score is slightly lower as no extra meaning is added.

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?

States a specific verb (delete) and resource (bucket), clearly distinct from siblings like nexusai_bucket_detach, nexusai_bucket_file_delete, or nexusai_volume_delete. An agent can immediately tell what this tool does.

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?

Provides a critical precondition: 'Must be detached from all deployments first.' This implies the detach tool (nexusai_bucket_detach) is a prerequisite, giving clear guidance on when not to call directly. However, it doesn't explicitly name the detach sibling or mention other uses.

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