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

Annotations already declare the full safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=false). The description adds the write-scope auth requirement, which is useful context beyond annotations, but says nothing about the non-idempotent duplicate-creating behavior or mutation caveats (the purchase-cost overwrite is disclosed only in the schema).

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, zero filler, with the purpose front-loaded and the prerequisite following immediately. 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 nine-parameter mutation tool with no output schema and complete schema coverage, the description covers purpose, auth scope, and the key prerequisite. It could still note non-idempotent duplicate risk, but nothing essential to correct invocation 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?

Schema description coverage is 100%, so parameters are fully documented structurally and the baseline is 3. The description adds only an operational note for resolving asset_id, not syntax or meaning for the other eight parameters.

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 a specific verb and resource ('Record a point-in-time condition assessment against an asset'), which is clearly distinct from sibling create_asset_status or create_asset_lifecycle_event. It does not explicitly name an alternative or sibling, so it stops short of full differentiation.

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?

It gives a concrete prerequisite ('Call list_assets first to resolve asset_id') and the required scope, which tells the agent how to prepare. However, it offers no guidance on when to use this versus update_asset_condition_assessment or what to do for an existing assessment.

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