products_batch_read

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a read operation but doesn't mention permissions required, rate limits, pagination behavior, error handling, or what happens with invalid IDs. The description lacks crucial context about how the batch operation behaves (e.g., partial successes, ordering of results).

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 appropriately concise with two sentences that directly address the tool's purpose. It's front-loaded with the core functionality. However, the second sentence is somewhat redundant with the first and could be more efficiently structured.

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 batch read tool with 4 parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain the return format, error conditions, authentication requirements, or how the batch operation scales. The description leaves too many open questions about a non-trivial batch operation.

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 schema provides no parameter documentation. The description only mentions the idProperty parameter and vaguely references 'internal ID' and 'unique property values' without explaining the inputs array structure, what properties/propertiesWithHistory arrays contain, or how these parameters interact. Four parameters exist with zero documentation in schema, and the description adds minimal semantic value.

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 reads a batch of products using internal IDs or unique property values, which is a specific verb+resource combination. It distinguishes from sibling tools like products_list or products_search by focusing on batch retrieval by IDs/properties rather than listing or searching. However, it doesn't explicitly contrast with products_read (singular read) or products_batch_create/update.

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 like products_list, products_search, or products_read. It mentions the idProperty parameter but doesn't explain when batch reading by IDs is preferable to other retrieval methods. No exclusions, prerequisites, or comparison to sibling tools are provided.

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