products_get

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

The description lacks explicit behavioral disclosure such as stating it is read-only or discussing side effects, permissions, or rate limits. Since no annotations are provided, the description carries full burden, but the purpose is straightforward and non-destructive by nature.

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, well-structured into two paragraphs: first stating purpose and listing returned data, second giving usage examples. Every sentence adds value, making it efficient and front-loaded.

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 provides a comprehensive list of returned data categories, compensating for the absence of an output schema. For a simple get operation with one parameter, this is complete and highly informative.

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 coverage is 100% with the single 'id' parameter described as 'Product ID'. The description does not add additional parameter semantics beyond what the schema provides, but it is not necessary. Baseline 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 it gets detailed information about a specific product and lists the data categories returned. It distinguishes itself from sibling tools like products_list and products_search by focusing on a single product by ID.

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 explicit use cases (e.g., viewing complete specifications, getting pricing) and implies the tool is for single-product detail retrieval. It does not explicitly mention when not to use it or alternative tools, but the context with sibling tools makes the usage clear.

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