get_product_info

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

No annotations are provided, so the description carries the disclosure burden. It adds valuable context by stating the data is 'fake internal', which sets expectations about its nature. The verb 'Retrieve' strongly implies a read-only operation, covering the safety profile despite lacking explicit 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 sentences, front-loaded with the action and purpose, and every sentence adds value. The examples are concise and directly useful for invoking the tool.

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 simple tool with one parameter and an output schema present, the description covers what it does, how to pass the product ID, and gives realistic examples. No additional return format explanation is needed since the output schema exists.

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 0%, but the description compensates by giving concrete example values (MORTGAGE-FLEX, PAYMENT-PLUS, BUSINESS-ACCOUNT) and clarifying that the parameter is a product ID. This adds meaning beyond the bare 'string' type in the schema.

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 uses a specific verb 'Retrieve' with a clear resource 'fake internal product information' and method 'by product ID'. This clearly distinguishes it from sibling tools like get_customer_profile and get_api_endpoint_info.

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 by providing example product IDs, but it does not explicitly state when to use this tool over alternatives or mention exclusions. Sibling names suggest distinct purposes, but the description itself offers no direct comparison.

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