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

Given the annotations already declare readOnlyHint and idempotentHint, the description adds value by disclosing the bulk support behavior (accepting an array of ids for batched execution) and referencing the underlying script. This is beyond what annotations provide, though it does not cover other aspects like auth or error handling.

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 extremely concise, consisting of two sentences. The first sentence front-loads the core purpose, and the second adds the bulk capability. There is no fluff or redundant information, making it highly efficient.

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?

The description covers the main functionality (getting product details) and mentions batch support, but it leaves the 'account' parameter unexplained and does not describe the return format or any limitations. Given no output schema, this is a moderate gap, but the description is adequate for a simple read 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?

The input schema has zero description coverage, so the description must compensate. It explains the 'id' parameter (by id) and mentions 'ids' for bulk support, but does not explain the 'account' parameter. This partially compensates for the missing schema descriptions but is not comprehensive for all three parameters.

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 that the tool details a product by id, which is a specific verb+resource. It also mentions bulk support for multiple ids, adding scope. However, it does not explicitly differentiate from sibling tools like tiny_get_product_stock or tiny_list_products, so it is clear but not fully distinct.

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 implies usage for retrieving product details, but provides no explicit guidance on when to use this tool versus alternatives. It does not mention when not to use it, nor does it name any alternative tools. The context is implied but lacks exclusions or comparisons.

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