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

No annotations are provided, so the description carries the full behavioral burden. It discloses the returned fields (pricing, tiers, GST, stock, options, URL), which aids the agent, but does not explicitly state read-only nature, permission requirements, or rate limits.

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?

One dense sentence that front-loads the purpose and enumerates return fields without filler. The list is long but every item is relevant to what the tool returns.

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 single-parameter read tool with no output schema, the description adequately covers the returned data: description, pricing, bulk-discount tiers, GST rate, minimum order quantity, stock signal, options, and page URL. It is sufficient for an agent to invoke and interpret the response, though it does not address error cases or permissions.

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 100% and documents the single slug parameter. The description adds useful semantic context beyond the schema by noting the slug originates from search-products results and that a numeric id is also acceptable.

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?

States a specific verb and resource: 'Full public details for one product or bundle by its permalink slug ... or numeric id.' It distinguishes itself from search-products by indicating the slug comes from those results, and it explicitly covers both products and bundles.

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?

Provides clear usage context by noting the slug comes from search-products results, implying this is the follow-up detail call. It does not explicitly name alternatives or state when-not to use it, but the context is clear.

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