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 adds real context beyond that: results are restricted to "currently requestable" inventory from registered companies, and it discloses the cursor-based pagination contract, which is exactly the behavior an agent needs to loop correctly.

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 sentences, both earning their place, with the core scope stated first and pagination second. The returned-field list is compact and justified because no output schema exists; nothing is padded or repeated.

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 two-parameter, zero-required read tool with full annotations, the description covers scope, returned fields and pagination adequately. The remaining gap is the undocumented locale parameter, which is a modest omission rather than a blocker for calling the tool.

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 pagination sentence reinforces the meaning of the cursor parameter ("nextCursor from a previous call"), which the schema already documents. With schema coverage at 50%, the locale parameter has no description anywhere and the description does not compensate by explaining what locale changes (response language, formatting, availability).

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 ("List") with a scoped resource ("currently requestable machines from registered rental companies") and names the payload fields returned (equipmentId, specifications, delivery options). It does not distinguish itself from the sibling search_rental_offers, so an agent cannot tell from the description alone which of the two to reach for.

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?

Gives one concrete usage instruction: paginate with the returned nextCursor. It offers no guidance on when to call this versus search_rental_offers, nor any exclusions or prerequisites, so the agent must infer the catalog-versus-search distinction from names alone.

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