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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds two pieces of genuinely new context: that the delete is a SOFT delete (record is not physically removed) and that it requires the asset_condition_assessments:write scope, which is an authorization requirement not present in the annotations.

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?

Two short sentences, front-loaded with the action and resource; the permission requirement is the second sentence. Nothing is redundant or padded.

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 full annotation coverage, the definition covers action, target, key, deletion semantics, and required scope. Minor gaps remain (cascading effects on related records, and no output schema describing the response), but nothing essential to invoking it correctly 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?

The single 'id' parameter has 100% schema description coverage (uuid, described as 'Assessment ID'), so the schema carries the semantics. The description only echoes 'by ID' and adds no format, validation, or lookup guidance beyond what the schema provides, which is the baseline 3 case.

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 ('Soft-delete an asset condition assessment') plus the lookup key ('by ID'), so the agent knows exactly what the tool acts on. It does not explicitly distinguish itself from sibling mutation tools like update_asset_condition_assessment, but the unique resource name makes the target 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?

There is no guidance on when to use this versus update_asset_condition_assessment (soft-delete vs. inactivate vs. modify) or any sibling. The only usage signal is the implied one from the verb 'delete'; no exclusions, prerequisites, or alternatives are named.

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