Catalog_GetProductBySku

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

No annotations are provided, so the description carries the full burden. It only says 'Get product' which implies a read operation, but fails to disclose any other behavioral traits such as whether it is read-only, any authentication requirements, rate limits, or side effects. The minimal description does not sufficiently compensate for the missing annotations.

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 very short, but it could be more informative. While concise, it sacrifices clarity and completeness. A brief description like this is minimally adequate but does not provide enough information to be considered well-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?

Given the tool has no output schema, the description should hint at what is returned. It does not. Additionally, among a large set of sibling tools, more context about the purpose and data returned would be beneficial. The description feels incomplete for a retrieval 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 100% description coverage for the single parameter 'sku'. The description 'Get product by Sku' adds no additional meaning beyond the schema. Given high schema coverage, baseline score of 3 is appropriate.

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 verb 'Get' and the resource 'product by Sku'. It is specific enough to indicate the tool's core function, but does not explicitly differentiate from siblings like Catalog_GetProductByProductId, which retrieves by a different identifier.

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?

There is no guidance on when to use this tool versus alternatives such as Catalog_GetProductByProductId or Catalog_GetProducts. The agent receives no context about which tool is appropriate under different conditions.

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