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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description adds the underlying endpoint (GET /asset) and the fact that results are assets scoped to customer locations, but it omits any pagination behavior despite page/limit parameters existing.

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 short sentences, front-loaded with the core purpose and followed by the API route. Nothing is padded, though the endpoint reference is marginally less useful to an agent than a usage rule would have been.

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 8 optional filter parameters and no output schema, the description should clarify the shape of returned records and pagination. It names three returned fields (type, status, name), which helps, but leaves the response envelope, total counts, and paging behavior unexplained.

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 eight parameters (including name, type, status, locationId, jobId) are already fully documented. The description only echoes the type/status/name filters and adds no syntax or semantics beyond the schema, so the baseline of 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 verb+resource ('List assets') and even defines the domain object with examples (extinguishers, panels, pumps), so an agent knows exactly what it retrieves. It implicitly separates itself from the singular get_asset sibling, though it never names that alternative.

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 guidance on when to use this list endpoint versus servicetrade_get_asset, nor when to apply which filter. The only hint is the phrase 'at customer locations', which implies a location-scoped listing but does not state it as a usage rule.

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