GET /companies

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered. The description adds nothing behavioral beyond that — no mention of pagination behavior, default page size, or what a listing contains; the note about being generated from the Snipe-IT OpenAPI operation explains provenance, not behavior.

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 with the core action front-loaded. The trailing "Generated from Snipe-IT OpenAPI operation companies." largely restates the tool name and is close to filler, but it is short enough not to hurt.

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 no output schema, the description should say what a listing returns (array shape, pagination metadata), and it only says "a listing of companies." The annotations cover safety and the schema covers inputs, so this is adequate but thin for the return-value side.

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% with all six parameters documented, including the codegen-added sort/limit/offset/search caveats, so the baseline is 3. The description adds no meaning about how name/search filters interact with the listing or how limit/offset paginate.

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 ("Return a listing of companies") plus the HTTP route, so the agent knows it is a read-only list endpoint. However, it gives no clue how it differs from the closely-named sibling snipeit_gen_companies_1, leaving the agent to guess between duplicate codegen variants.

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 snipeit_gen_companiesid, snipeit_gen_companies_1, or snipeit_raw_request. No preconditions, no filtering/pagination guidance, no exclusions — the agent must infer everything from the name.

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