Search items

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

The description adds value beyond the readOnlyHint annotation by explicitly stating 'Read-only' and disclosing the return format: 'Returns a page of items plus the total record count.' It does not contradict 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?

Two sentences, front-loaded with purpose, followed by filters and return info. No wasted words, highly scannable.

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 28-parameter search tool with no output schema, the description gives a solid high-level overview: purpose, main filters, and response shape. It relies on the schema for parameter details, which is appropriate.

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 low (25%), but the description lists many key filter fields: serial, manufacturer, model, type, caliber, status, date ranges, TTSN/OTSN, and 'and more.' It doesn't fully compensate for all 28 parameters, but it conveys the main searchable dimensions.

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 'Search the firearm inventory (the A&D book)' with a specific verb and resource. It is distinct from sibling search tools like search_acquisitions and search_dispositions by naming the inventory context.

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?

Provides clear context: this searches items in the A&D book and lists filterable fields. It does not explicitly name alternatives or state when not to use it, but the scope is well-defined.

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