get_product

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

Specifies HTTP GET, implying read-only operation. No annotations present, so description carries burden. Lacks details on error handling, authentication, or rate limits, which are common for a retrieval tool.

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?

Extremely concise: three distinct pieces of information (purpose, endpoint, optional parameter) in one sentence, no filler words.

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 get tool with no output schema, description omits return value details and common error scenarios. While adequate for basic use, more completeness would improve agent effectiveness.

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?

Adds context beyond schema by indicating productId is a path parameter ('GET /products/{productId}') and that include is optional. Schema already covers both parameters with descriptions, so extra value is moderate but helpful.

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?

Clearly states 'Get a product by ID' with specific verb and resource. Includes HTTP method and path for clarity. Distinguishes from sibling list/get tools by focusing on single product retrieval 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?

Description implies usage when you have a product ID, but does not explicitly contrast with list_products or other getters. No when-not-to-use or alternative guidance is provided.

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