Get asset condition assessment

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

Annotations already declare the safe read-only, idempotent, non-destructive profile, so the bar is lower. The description adds genuinely useful context beyond them: how to interpret the 0-100 score bands (85+ Excellent through below 40 Critical) and the caveat that amounts are bare numbers requiring get_organization_settings for currency_code.

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, front-loaded with the core action and then the two interpretation rules. Every sentence earns its place; nothing is padding, though the score-band enumeration is the bulkiest element.

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?

With no output schema, the description wisely covers the two ambiguous output elements an agent would trip on: the score scale and the currency-less amounts. It does not describe error behavior for a missing ID, keeping it just short of complete.

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% for the single required 'id' parameter (uuid format, pattern), so the schema already carries the semantics. The description restates 'by ID' without adding format or lookup guidance beyond it, which matches the baseline 3.

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 (Get) and resource (a single asset condition assessment) scoped by ID, which cleanly distinguishes it from the sibling list_asset_condition_assessments. It does not name siblings explicitly, so it falls 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 'by ID' phrasing implies this is the retrieval path for a known identifier rather than browsing, but it never states when to use this versus list_asset_condition_assessments or what to do if the ID is unknown. Usage is implied rather than guided.

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