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

With no annotations provided, the description carries the full behavioral burden. It explicitly states 'Reads only,' signaling a safe non-mutating operation, and discloses what fields the response includes. It does not discuss pagination, volume, or errors, but for a simple read-only tool this is adequate.

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?

The description is a single dense sentence that front-loads the core action and then lists the returned details. It is efficient with no filler, though the long enumeration could be lightly structured for readability.

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?

Given a simple 1-parameter read tool with full schema coverage and no output schema, the description provides the key contextual facts: how to identify the asset, what data comes back, ordering, and that the operation is read-only. It is complete enough for correct invocation, with only minor gaps around response size or error behavior.

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?

The schema already describes the single parameter completely, including examples and the uniqueness condition for name-based lookup. The description's 'by id, tag or name' slightly paraphrases the schema but adds no substantial new semantic information, so the baseline 3 is appropriate.

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 uses a specific verb ('Read') with a clear resource ('one asset') and enumerates exact returned data: chronological log entries, total spend in cents and formatted, last service date, and next-due date. It clearly distinguishes this from sibling mutation tools like asset_add and asset_remove.

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 description makes the usage context explicit: call this when you need a single asset's full history and financial detail. It does not explicitly name alternatives or exclusions, so it stops short of a 5, but the context is clear enough for an agent to select it appropriately.

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