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

The readOnlyHint annotation already establishes that this is a safe read, so the description only needs to add context — but it adds almost none beyond restating the endpoint path. It says nothing about behavior when the number does not exist (error vs empty), whether auth/permissions are required, or what the response contains.

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 terse fragments with zero filler and the key qualifier ('one ... item by number') front-loaded. It is arguably too terse rather than bloated, but every word earns its place.

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 simple single-record read with full schema coverage and no output schema, the description is minimally sufficient. It is missing the disambiguation from ezrentout_get_asset and any note about missing-record behavior, which are the remaining gaps an agent would need.

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 coverage is 100%, so both parameters are fully documented in the schema; the description's 'by number' merely restates asset_number. It adds no meaning for include_custom_fields or for accepted number formats beyond what the schema's pattern already specifies, so the baseline 3 applies.

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 states a specific resource — a single asset stock item retrieved by number — and even cites the underlying endpoint, so the singular-fetch semantics are explicit. However, it does not differentiate this from the similarly named sibling ezrentout_get_asset or from ezrentout_list_asset_stock, leaving the agent to infer when 'stock asset' differs from 'asset'.

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?

There is no explicit when-to-use guidance, no mention of prerequisites, and no pointer to alternatives such as ezrentout_list_asset_stock or ezrentout_filter_assets. The agent must infer usage from the name alone.

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