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

Despite destructiveHint=true already flagging danger, the description adds real context the annotation cannot: exactly what is destroyed (release objects, plus chart/operator-deleted data, with a ConcretePG-style example), what delete_permanently=false preserves (definition, not data), and a hard refusal condition on managed-service stacks.

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?

Dense but front-loaded: purpose first, then destruction semantics, then the delete_permanently branch, then the refusal. Every sentence carries decision-relevant information, though the parenthetical about CloudNativePG is the one slightly expendable clause.

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 destructive, non-idempotent mutation with no output schema, the description covers data-loss scope, reversibility, default behavior, and refusal cases -- everything an agent needs before invoking it.

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 earns an extra point by explaining the semantic consequence of delete_permanently (restorable definition vs. permanent removal) and citing the REST API default, refining rather than repeating the schema text.

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+resource ('Mark an addon for uninstallation from a deployed stack') and immediately scopes it against the draft-based siblings ('without going through the draft system'), distinguishing it from add_addon_to_stack_profile_draft / remove_addon_from_stack_profile_draft and from rollback_addon.

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?

Gives explicit when-to-use ('direct removal of a single addon'), when-to-use delete_permanently=true ('only when the user explicitly wants the addon permanently deleted'), and a when-not with a named alternative ('An addon of a stack a managed service owns is refused: retire the service instead').

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