Get product

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds behavioral context by indicating that related data is not included by default and must be explicitly requested via 'with', which is a useful trait beyond the 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 two concise sentences, front-loaded with the primary purpose. Every word adds value: the first sentence states the tool's function, and the second explains the optional 'with' parameter with concrete examples. No wasted text.

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 read-only tool with only two parameters, strong annotations, and no output schema, the description is adequately complete. It covers the core function and the key parameter behavior, though it doesn't elaborate on the exact composition of 'full product details' or any potential response variations.

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 schema already covers both parameters with descriptions (100% coverage), so the baseline is 3. The description enriches meaning by enumerating valid relation names for 'with', going beyond the schema's example and providing a more complete reference for parameter values.

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 'Get full product details' with a specific verb and resource. It distinguishes from sibling tools like list_products by focusing on a single product's details, and from get_product_prices by mentioning inclusion of multiple related data sets via the 'with' parameter.

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 usage context is implied (retrieve a product by ID), but there is no explicit guidance on when to use this tool versus alternatives like list_products or get_product_prices. The only direct guidance is how to use the 'with' parameter, not when to choose this tool over others.

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