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

readOnlyHint=true already covers the safety profile, so the description only needs to add context. It discloses the backing call ('GET /search.api, facet FixedAsset') and the query prefixes, but says nothing about matching semantics (prefix vs substring), empty-result behavior, or what the response looks like beyond the pagination hint in the schema.

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?

A single front-loaded sentence that leads with the matching rules; nothing is padded. The trailing 'GET /search.api (facet FixedAsset)' is implementation detail of marginal value to an agent choosing a tool, but it costs little.

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 only two parameters and annotations present, the basics are covered, but there is no output schema and the description never indicates what comes back (a list of asset records?) or how it differs from the several sibling search/list/filter tools. An agent can call it, but not confidently instead of the alternatives.

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 the baseline is 3. The description largely repeats the schema's own text ('Name, #<item number> or @<identification number>'), with the one genuinely new constraint being the '3+ characters' minimum, which notably conflicts with the schema's minLength of 1.

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 (search) and resource (assets) plus the accepted query syntaxes, so the agent knows exactly what the tool matches on. It does not distinguish itself from near-neighbors like ezrentout_filter_assets, ezrentout_list_assets, or ezrentout_search_inventory, which is the only thing keeping it from 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?

No guidance on when to use this versus filter_assets (structured filtering) or list_assets (enumeration) or search_inventory (non-asset items). The usage is only implied by the syntax description, and there are no stated exclusions or alternatives.

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