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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive), and the description adds genuinely useful context beyond them: the API-key requirement, the 'when permitted' conditional on stock, and an honest caveat that tier pricing and lead time are placeholders until the Acumatica sync ships. That last point is exactly the kind of data-quality disclosure an agent needs.

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 tight sentences, front-loaded with the core capability before the auth prerequisite and the placeholder caveat. No filler, though the parenthetical '(when permitted)' is slightly vague.

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-SKU lookup with no output schema, the description does enough: it names the returned fields (price, availability, stock) and warns that lead time and tier pricing are not yet real. It stops short of describing return format or error behavior, but nothing critical for correct invocation is missing.

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?

Only one parameter, and schema description coverage is 100%, so the schema already documents 'sku' fully. The description adds no syntax, format, or validation detail about the SKU, so it sits at the baseline.

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 (Get) and concrete resources (current price, availability, stock) scoped to a SKU. It is distinguishable from siblings like get_product_details and request_quote, though it never explicitly contrasts itself with them.

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?

Usage is only implied — an agent can infer this is for pricing lookups on a known SKU, and the 'KEYED tool — requires a valid API key' line gives a real prerequisite. But there is no explicit when-to-use versus get_product_details or request_quote, and no exclusions.

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