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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description's main job is to add operational behavior — which it does by disclosing that results are keyset-paginated and returned one page at a time. It does not mention rate limits, filter semantics, or ordering guarantees, so it is good but not exhaustive.

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?

Three short sentences with the resource definition and disambiguation front-loaded, followed by the endpoint and the paging contract. No filler, no restatement of 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 13-parameter, all-optional list tool with no output schema, the description covers the essentials: what is listed, the endpoint, and the paging model including how to advance pages. It stops short of describing the shape of returned equipment records, which is the one gap given no output schema exists.

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 description coverage is 100%, so all 13 parameters are already documented in the schema. The description's only parameter-related statement — using next_cursor as start_cursor — restates what the start_cursor schema description already says, adding no new meaning. Baseline 3 applies when the schema does the heavy lifting.

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 ('List equipment') and immediately disambiguates the resource as 'non-vehicle assets such as trailers and tools', which separates it from the large family of vehicle-list siblings. It also pins the underlying endpoint (GET /equipment). An agent can distinguish this from fleetio_list_vehicles without opening either schema.

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 gives pagination guidance ('pass next_cursor as start_cursor'), which is useful operational context, but never states when to prefer this over alternatives such as fleetio_get_equipment for a single asset or fleetio_list_vehicles for vehicles. Usage is implied by the resource name rather than spelled out, and none of the available filters are advertised.

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