capabilities

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile and locality are known without the description. The description contributes the scope of what is reported (formats, hardware, workspace, limits), but adds nothing about cost, caching, or whether results can change between calls (e.g., after hardware changes) — the sort of context that would exceed the annotations.

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?

A single short sentence with the action front-loaded and the four categories of returned information listed compactly. No filler, no repetition of the tool name or title.

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 an output schema present, the description need not explain return values; it only has to signal what the tool is for, which it does via the enumerated categories. For a zero-parameter, read-only tool this is nearly sufficient — the only missing piece is a hint about when in a workflow to call it.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description correctly implies a no-argument call by not referencing any inputs.

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?

"Report supported formats, hardware, workspace, and operational limits" gives a specific verb (report) and enumerates exactly what information the tool surfaces, so an agent knows it is a static self-description/query endpoint rather than an action on data. It does not explicitly separate itself from a similarly generic sibling such as "inventory", which keeps it out of 5 territory.

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 when-to-use statement or exclusion, but the nature of the call (a zero-argument capability query) makes the appropriate context strongly implied: check it before attempting operations whose format/hardware support is uncertain. No prerequisites or alternatives are named.

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