search_items

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

No annotations provided, so description must disclose behavior. It indicates a read operation (search) but fails to mention side effects, rate limits, authentication needs, or pagination behavior. The reference to 'node-quickbooks findItems' adds implementation detail but not behavioral transparency.

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 one sentence, concise but lacking essential details. The parenthetical about 'node-quickbooks findItems' is potentially confusing and adds no value for the agent. It achieves conciseness but at the cost of completeness.

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 lack of output schema, annotations, and only 50% schema coverage, the description is severely incomplete. It does not explain the criteria format, search behavior, result structure, or handling of multiple results. For a search tool with complex parameters, this is insufficient.

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 description adds little beyond the schema: 'using criteria' echoes the criteria property without explaining its structure or allowed values. The company parameter is already described in the schema. Schema coverage is 50%, but the description does not compensate for the undocumented criteria.

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?

Clearly states it searches items in QuickBooks Online using criteria, distinguishing it from other search tools (e.g., search_accounts, search_customers). The verb 'search' and resource 'items' are specific, but the description could better clarify what types of items are included.

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?

No guidance on when to use this tool versus alternatives (e.g., read_item for a single item, create_item for adding items). Does not mention prerequisites, exclusions, or context for using criteria-based search.

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