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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real value beyond them: 'Financial fields are role-restricted' signals permission-dependent field visibility, and 'explicitly approved document resource URIs' signals that returned URIs are access-filtered.

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 sentences: usage condition first, then returned content, then the access caveat. No filler, no restatement of the title, and the most decision-relevant line (when to use it) is front-loaded.

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?

There is no output schema, so the description carries the return-value burden and does so by enumerating specs, status, lifecycle data and document URIs. Missing only edge behavior such as what happens for an unknown or unauthorized assetId, which is a minor gap for a single-parameter read.

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?

Only one parameter (assetId) and the schema gives it 0% description coverage — no format, no source, no example. The description only implies 'one known asset', which hints at a single identifier but adds nothing about the ID's origin or constraints (maxLength 255, non-empty).

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?

Uses a specific verb ('Get') with a named resource ('asset specifications, status, lifecycle data and ... document resource URIs'), and the phrase 'one known asset' scopes it to a single-record lookup. It does not name the nearby siblings (search_assets, view_asset, get_asset_service_history) it should be distinguished from, so an agent must infer the boundary.

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?

'Use this when inspecting one known asset' gives a clear triggering condition and implicitly separates this from search/discovery tools by requiring a known ID. No explicit exclusions or named alternatives are given, so the agent has to derive the rest from the sibling list.

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