get_product

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

No annotations are provided, so the description carries the burden. It correctly implies this is a read-only operation (get info). It does not mention any side effects, permissions, or rate limits, but for a simple retrieval tool, this is largely sufficient. A small deduction for not explicitly stating it is non-destructive.

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 with no unnecessary words. The description front-loads the purpose and provides a clear note about when to use it. Highly efficient.

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?

While the description covers purpose and usage, it does not describe what 'detailed information' includes or the return structure. There is no output schema. Given the simplicity of the tool, the lack of return details is a notable gap, though siblings may provide context.

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?

There is one parameter, offer_id, with a schema description. The tool description adds context that the ID comes from search results, which is helpful. Schema coverage is 100%, so the description adds marginal value beyond the schema but still reinforces the source of the ID.

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 the tool gets detailed information about a specific product offer, using the verb 'get' and specifying the resource 'product offer'. It distinguishes from sibling tools like search_products by noting that search results already contain full details, so this tool is for refreshing data.

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 explicitly tells when to use this tool (when you need to refresh data) and when not to (search results already have full details). It implies the alternative is search_products, providing clear guidance.

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