GET /hardware/audit/due

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that results are assets due for auditing soon, but it does not disclose pagination behavior or response shape. With annotations doing most of the work, this is adequate but not rich.

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?

The description is short and front-loads the purpose in the first sentence. The second sentence about being generated from the Snipe-IT OpenAPI operation adds little invocation value, but the overall text remains compact and easy to scan.

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 simple read-only list operation with full schema coverage and strong annotations, the core purpose is covered. However, no output schema exists and the description does not clarify how this differs from the near-identical snipeit_list_audit_due sibling or what the returned asset list contains.

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 the schema already documents all five optional parameters. The description adds no parameter-level meaning such as default sort order, search scope, or pagination limits beyond what the schema provides.

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 and resource: retrieve a list of assets due for auditing soon. It is clear what the tool returns, but it does not distinguish this operation from sibling tools such as snipeit_list_audit_due, snipeit_list_audit_overdue, or snipeit_gen_hardwareauditoverdue.

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 no explicit when-to-use guidance, no exclusions, and no alternatives. An agent must infer whether to call this tool versus the similarly named snipeit_list_audit_due or the overdue-audit siblings.

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