get_product

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

Annotations declare readOnlyHint=true, consistent with a read operation. Description adds critical behavior: include_raw dumps entire untouched payload and overrides all flags. No contradictions.

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?

Two sentences: first states purpose and default data, second enumerates opt-in flags with a concise rule for include_raw. No wasted words, front-loaded with essential info.

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 tool with 8 parameters, no output schema, and no nested objects, the description covers default outputs, opt-in flags, and the include_raw override. Does not explain return format or error conditions, but given context, it's largely sufficient.

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?

All 8 parameters have schema descriptions (100% coverage). Description adds value by explaining what each opt-in flag includes (e.g., 'converted to Markdown' for specs, 'with prices and ETAs' for delivery) and notes that variations summary is always shown.

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?

Description explicitly states 'Get full details for one KSP product by UIN or URL' and lists the data fields. It differentiates from siblings: get_product is for single product details, while search_products is for search, get_product_images for images only, and get_filters for filters.

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?

Description explains default returns (price, promo, stock, variations) and opt-in flags. It implicitly guides when to use this tool (single product lookup) vs siblings, but lacks explicit 'use this when' or 'not for' statements.

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