query_items

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

No annotations are provided, so the description carries the full burden. It discloses the read-only nature (by verb 'query'), lists supported filter operators, and gives an example, but lacks details on default limits, maximum allowed values, or any side effects. It is adequate but not comprehensive.

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 concise with three clear parts: purpose statement, list of operators, and an example. It is front-loaded and each sentence adds value, though it could be slightly more structured with bullet points for the operators.

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 complexity (11 parameters) and no output schema, the description covers the core functionality with an example and operator list. It does not explain pagination behavior or return format, but the schema handles parameter details, so it is reasonably complete for typical use.

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 coverage is 100%, so baseline is 3. The description adds value beyond the schema by enumerating specific filter operators and providing a concrete example that demonstrates parameter usage (filter, sort, limit). This helps the agent understand how to construct queries.

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 it queries items with advanced filtering, sorting, pagination, and search, distinguishing it from sibling mutation tools (e.g., create_item, update_item) and other read tools like get_item. The verb 'query items' and specific capabilities make the purpose unmistakable.

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 implies use cases but does not explicitly state when to use this tool versus siblings like get_item or list_collections. It provides no guidance on exclusions or alternatives, leaving the agent to infer from the context.

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