query_items

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

No annotations are provided, so the description must disclose behavioral traits. It states 'Read item data,' implying read-only, but does not specify safety, side effects, rate limits, pagination, or output structure. The lack of detail leaves agents uncertain about the tool's behavior beyond the basic operation.

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 a single sentence that efficiently front-loads the purpose ('Read item data') and enumerates actions. However, the dense list could be better structured (e.g., using bullet points) for readability.

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?

Given the tool's complexity (9 parameters, multiple actions) and lack of output schema, the description is incomplete. It does not explain how to use filters, what responses look like, or how actions interrelate, leaving significant gaps for an agent to use the tool effectively.

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?

With 89% schema coverage, the input schema already provides most parameter descriptions. The description adds minimal extra meaning by grouping actions (e.g., 'all (list with optional filters)') but does not enrich parameter semantics beyond what the schema offers.

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 clearly states 'Read item data' which is a specific verb+resource pair. It then lists the various actions, adding context for each (e.g., 'all (list with optional filters)'). However, it does not explicitly differentiate this tool from siblings like query_rules or query_things, which also have clear names but could cause confusion.

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 lists actions and their basic purpose but provides no guidance on when to use this tool versus alternatives. For example, it does not explain when to use query_items over query_rules or query_things, nor does it mention prerequisites or exclusions.

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