simpleshop_find_documents

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

With no annotations, the description must disclose behavioral traits. It only states the basic operation, omitting details like pagination, sorting, filtering semantics, or whether the operation is read-only. The description adds minimal behavioral context beyond the schema.

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 concise sentence with no waste. It is front-loaded with the essential purpose, though the structure could include key parameter modes for clarity.

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 (many filters, pagination, and an output schema), the description is adequate but not complete. It explains the two modes but omits details like sorting, pagination, and flag filtering, which are documented in the schema. The high schema coverage mitigates the gaps.

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 100% (the complex input schema includes descriptions for most parameters). The tool description does not add anything beyond what the schema already provides, meeting the baseline of 3.

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 the tool's purpose: 'Find SimpleShop documents by search filters or explicit document IDs.' It uses a specific verb ('Find') and resource ('SimpleShop documents'), and distinguishes from sibling tools like `simpleshop_download_documents` (which downloads) and `simpleshop_find_products` (which finds products).

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 provides no guidance on when to use this tool versus alternatives, nor any conditions or exclusions. It lacks context for selecting between 'search' and 'by_ids' modes beyond what the schema example shows.

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