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

readOnlyHint=true already tells the agent this is a safe read. The description contributes one genuinely new behavioral fact — a fixed page size of 25 per page — which goes slightly beyond the schema's pagination wording. It says nothing about result shape, sort order, or whether the list is bounded, which is useful but not critical for a read-only lister.

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?

One sentence, front-loaded with the resource definition, then the pagination fact and endpoint. No filler, nothing repeated from 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?

For a two-parameter read-only lister with full schema coverage and annotations, this is close to sufficient — no output schema means return values need not be described. The remaining gap is sibling routing against search_inventory, which matters given how many inventory-adjacent tools exist.

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 page and include_custom_fields are fully documented in structured form and the baseline applies. The description only reinforces the pagination dimension by stating 25 items per page; it says nothing about include_custom_fields and adds no syntax beyond the schema.

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 plus a genuine disambiguation: inventory means 'consumable items tracked by quantity', which separates it from the many asset-oriented siblings. It does not, however, distinguish itself from the sibling ezrentout_search_inventory, so a routing decision between the two is left unexplained.

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 verb 'List' implies full enumeration versus targeted lookup, and the description supplies the GET endpoint. But it never says when to prefer this over ezrentout_search_inventory or ezrentout_get_inventory_item, and it gives no prerequisites or exclusions.

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