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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real domain behavior beyond that: the 0-100 score banding (85+ Excellent ... below 40 Critical) and the fact that monetary amounts are bare, currency-less numbers requiring a separate settings call.

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 compact sentences, front-loaded with the operation, then the two interpretive rules an agent genuinely needs. No filler or 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?

With no output schema, the description must convey how to read the response, and it does the important part: score-band interpretation and the currency caveat with the sibling call needed. It stops short of enumerating other returned fields, but nothing critical for correct invocation or interpretation 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% for the single 'id' parameter, so the schema already documents it fully ('Asset condition assessment ID', uuid format). The description's 'by ID' adds nothing beyond that; baseline 3 is appropriate given the schema does the heavy lifting.

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 ('Get a single asset condition assessment') plus the lookup key ('by ID'), which cleanly separates it from the sibling list_asset_condition_assessments. An agent can identify the tool's role without opening the schema.

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 clear operating context: single-record lookup by ID, and an explicit prerequisite action ('call get_organization_settings for currency_code before stating one'). It does not explicitly contrast with list_asset_condition_assessments, but the singular-by-ID framing makes the boundary obvious.

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