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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description earns credit for disclosing a concrete side effect beyond annotations: the asset's net book value and remaining life revert to their pre-betterment state, plus the auth scope required.

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: action, side effect, required scope. Front-loaded with the operation and zero filler, so every sentence 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 single-parameter delete with no output schema and safety fully covered by annotations, the description supplies purpose, the key side effect on the parent asset, and the auth requirement. It omits only idempotency/irreversibility framing, which the annotations already imply.

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 description coverage is 100% and the single id parameter is fully documented (UUID format, pattern, 'Betterment ID'). The description's 'by ID' adds nothing the schema doesn't already convey, so baseline 3 applies.

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 and resource ('Delete a betterment') and scopes it to 'by ID'. The verb cleanly separates it from get_/list_/update_/create_asset_betterment siblings, though the description never explicitly names an alternative, so it stops short of a 5.

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 action implies usage, and the required scope is noted, but there is no explicit when-to-use vs alternatives guidance, no warning about irreversibility, and no mention of prerequisites such as confirming the betterment exists. Guidance is only implied.

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