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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds no behavioral context of its own — no pagination, filtering behavior, default result limits, or auth requirements — and merely repeats the route.

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?

Very short, but the size comes from duplication rather than efficiency — the same endpoint string appears twice verbatim. It is not front-loaded with anything actionable, so the brevity is under-specification rather than conciseness.

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?

The tool takes two parameters with zero documented semantics, has no output schema, and exposes a free-form query object. Given that complexity, an agent cannot construct a valid or meaningful call from the description; it is forced to rely entirely on describe_operation.

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 0% and the schema itself is opaque: 'query' permits arbitrary additional properties and 'params' is an empty object with additionalProperties false. The description does not name a single supported query parameter or filter, so an agent has no way to know what can be passed; the pointer to describe_operation is the only mitigation.

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 is the endpoint string repeated twice: 'GET /api/inventory/items'. It restates the name and title rather than explaining what inventory items are returned, what the collection represents, or how it differs from siblings like get_inventory_items_by_id or get_inventory_stats. A read of a collection is implied, but nothing beyond the title is added.

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 when-to-use guidance, no exclusions, and no comparison to the many inventory siblings (assignments, categories, locations, stats, transactions). The only navigational hint is 'describe_operation provides native request schemas', which points at a schema lookup rather than telling the agent when this tool is the right choice.

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