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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds only the underlying endpoint (GET /assets); it says nothing about default page size, result caps, or what a page of results contains, which would be genuine added context for a list tool.

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 purpose, with no redundant restatement of the title. The trailing "GET /assets" is low-value for an agent since the HTTP route is not something it can act on.

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 read-only list endpoint with a 75%-documented schema and no output schema, the description covers what the tool does and its main filter axis. Missing details on the return payload (asset shape, next_page pagination behavior) are largely implied by the page/limit schema descriptions, so no critical gap remains.

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 75%, so page, limit and search are already documented; the notable gap is the status enum, which has no schema description. The phrase "by install status" partially compensates by tying status to install state, but it does not explain what each enum value means or how search interacts with status. Baseline 3 is appropriate.

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/search customer assets, i.e. equipment) plus the primary filter dimension (install status), which is enough to distinguish it from fieldpulse_get_asset (single-record fetch) and fieldpulse_list_asset_categories. It does not explicitly name any sibling, but the singular/plural and list-vs-get split makes the distinction inferable.

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?

"List or search ... by install status" implies both the browsing and the search use case, so usage is implied rather than stated. There is no explicit guidance on when to prefer this over fieldpulse_get_asset for a known ID, nor any prerequisites or exclusions.

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