List components

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without the description. The description adds only "paginated list," which is modest but real context about result shape; it omits anything about default page sizing, truncation behavior, or permissions.

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 clauses, front-loaded with the endpoint and resource, with no filler or redundancy. Brevity here is efficient if under-informative, but nothing in the text wastes the reader's space.

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 seven optional parameters, 29% schema coverage, and no output schema, the description carries real burden and does not meet it — the filter dimensions and the pagination/truncation contract are left entirely to the schema. An agent can call the tool, but must open the schema to know what it can filter on.

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 only 29% (two of seven parameters), so the description needs to compensate and does not: it never names company_id, category_id, or manufacturer_id, gesturing only at "common filters." It does flag that `search` exists, which is the one parameter meaning it adds beyond the schema's documented `all` and `limit`.

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 names a concrete verb and resource ("GET /components: paginated list") so an agent immediately knows it retrieves the components collection in pages. It does not, however, differentiate this tool from near-namesake siblings such as snipeit_gen_components or snipeit_gen_components_1, leaving the agent to guess which list endpoint is canonical.

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 statement of when to use this tool versus alternatives — nothing about preferring it over snipeit_gen_components or snipeit_raw_request, and no guidance on when pagination vs the `all` flag is appropriate. "Supports search and common filters" hints at a use case but names no condition or exclusion.

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