simpleshop_download_documents

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

No annotations provided and the description contains no behavioral details (e.g., failure modes, rate limits, authentication needs, or output format). The description fails to disclose any traits beyond the basic action.

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?

Extremely concise (one sentence) but at the expense of essential detail. Every sentence should earn its place; this one is too sparse to be adequately informative.

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 of batch-downloading documents (multiple parameters, output schema exists but unmentioned, constraints like max 100 items), the description is grossly incomplete. No information on result format, error handling, or limits.

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 0%. The description does not explain what the 'documents' array items represent, the meaning of 'variant' (with/without stamp), or the purpose of 'max_bytes'. With only 2 parameters, this omission is critical.

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 action (batch-download) and resource (PDF rendering of SimpleShop documents), distinguishing it from sibling tools like 'simpleshop_find_documents'.

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 vs. siblings such as 'simpleshop_find_documents' or 'simpleshop_find_products'. No context on prerequisites or exclusions.

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