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

The description discloses hidden side effects (initializing/updating internal records and recording an offer-view event) and exclusions (no cart, order, or payment), but it contradicts the idempotentHint annotation. Recording an event on each call suggests repeated identical calls produce additional effects, which conflicts with idempotency. This is an annotation contradiction.

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?

The description is compact, using two sentences to cover retrieval, side effects, and exclusions. It is well-structured and front-loads the primary purpose without unnecessary verbosity.

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?

The description covers side effects, disabled-offer behavior, and excluded operations, while the output schema is available for return details. It lacks explicit error scenarios and SKU acquisition context, but for a simple single-parameter read-like tool, it is reasonably complete.

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?

The description maps the single 'sku' parameter to the offer being retrieved, and the schema defines its type and length. It does not add significant detail about SKU format, source, or validation rules, but the parameter is simple and the description provides basic meaning.

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 retrieves one enabled exact Homebridge offer by SKU, using a specific verb and resource. It distinguishes itself from sibling tools like catalog, variant, and checkout tools by emphasizing 'exact' and 'enabled' offer retrieval and explicitly excluding cart/order/payment actions.

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 implies usage for fetching a single exact offer by SKU, but it does not explicitly state when to prefer this tool over siblings such as resolve_homebridge_major_variant or get_homebridge_major_category_catalog. It lacks direct when-to-use/when-not-to-use guidance.

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