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

Annotations already carry readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds genuinely non-obvious behavior — fuzzy partial-title matching and the recoverable error that enumerates the store's products. It supplies domain framing (products are sold on the store page, paid via the business's own Stripe) that clarifies this is admin-side, not a checkout. No pagination/size caveats, but for a single-record fetch that is minor.

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?

Dense but every clause carries information; the fuzzy-match and error-fallback details earn their place. The drawback is ordering: the actual "Read one store product in full" sentence arrives third, after two sentences of store-domain preamble, so the core action is not front-loaded.

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?

With no output schema, the description compensates by enumerating the returned fields, including type-specific content shapes (module/lesson outline for courses, billing interval for memberships, items for bundles). Combined with readOnly annotations and full schema coverage, an agent has everything needed to call it and interpret the result.

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%, so baseline is 3; the description earns the extra point by adding semantics the schema lacks — that the identifier may be a *partial* title and that a miss returns a list of candidate products. It does not explain workspaceId, but the schema already documents its default.

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?

"Read one store product in full" states a specific verb and single-resource scope, and the enumeration of returned fields (price, stock limit, refund policy, files, order bump, units sold, URL, content) makes clear this is the detail/fetch counterpart to list_store_products. It also names update_store_product as the mutation path, so the boundary with siblings is legible without opening a schema.

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?

It tells the agent exactly which identifier to source ("by id, slug or title from list_store_products"), notes that a partial title also matches, explains the failure path ("if nothing matches the error lists the store's products"), and explicitly routes mutations to update_store_product.

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