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

With annotations already declaring readOnly=false, destructive=false and idempotent=false, the safety profile is covered. The description adds genuine value by disclosing the required write scope (asset_condition_assessments:write) and the point-in-time nature, but it omits the notable irreversible side effect (overwriting purchase cost via update_purchase_cost), which is disclosed only inside 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?

Two tightly written sentences with the core purpose front-loaded and the prerequisite/auth details following. No filler, no restatement of the title.

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 create endpoint with 100% schema coverage and no output schema, the description covers the essential context: what it records, the required scope, and the prerequisite lookup. The one gap is that the description could flag that recording an assessment does not by itself change purchase cost, but the schema carries that detail.

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 the schema already documents all nine parameters, including the detailed update_purchase_cost semantics. The description only adds a hint about resolving asset_id, which is marginal beyond what the parameter's own description provides, so the baseline 3 holds.

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 (Record) and resource (point-in-time condition assessment against an asset), which is more precise than a generic 'create assessment'. It implicitly separates itself from sibling creates like create_asset_cost or create_asset_status by naming the condition-assessment concept, though it never calls out those siblings directly.

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 an explicit workflow prerequisite ('Call list_assets first to resolve asset_id') that tells the agent how to obtain a required input. It stops short of stating when NOT to use it or naming update_asset_condition_assessment as the alternative for editing an existing record.

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