products_batch_read

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a read-only operation ('Read', 'Retrieve'), which is consistent with the tool name, but doesn't specify whether it's safe, idempotent, or has side effects. It lacks details on rate limits, authentication needs, error handling, or return format, leaving significant gaps for a batch operation tool.

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 two sentences that directly address the tool's function. It's front-loaded with the main purpose and avoids unnecessary fluff. However, the second sentence is somewhat redundant with the first, slightly reducing efficiency.

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 a batch read tool with 4 parameters (3 required), 0% schema coverage, no annotations, and no output schema, the description is incomplete. It doesn't explain parameter interactions, return values, error cases, or how it differs from sibling tools. For a tool with significant contextual needs, this provides inadequate guidance.

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%, so the description must compensate for undocumented parameters. It only mentions 'idProperty' for retrieving records by custom unique values, ignoring 'productIds', 'properties', and 'propertiesWithHistory'. This leaves three required parameters and their interactions unexplained, failing to add meaningful semantics beyond the bare schema.

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: reading a batch of products by internal ID or unique property values. It specifies the verb ('Read'), resource ('products'), and scope ('batch'), distinguishing it from single-read tools like 'products_read'. However, it doesn't explicitly differentiate from other batch operations like 'products_batch_archive' or 'products_batch_update' beyond the read action.

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 minimal usage guidance, mentioning retrieval by 'idProperty' parameter for custom unique values. It doesn't explain when to use this tool versus alternatives like 'products_list', 'products_search', or 'products_read', nor does it mention prerequisites or constraints. The guidance is limited to parameter usage without broader context.

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