win_back_offers_get_instance

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

No annotations are provided, so the description carries the full burden, and it discloses nothing: no auth requirements, no side-effect profile, no rate limits, no mention of the relationship-inclusion behavior implied by the schema.

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?

It is short, but the second half is a pure duplication of the same route in parentheses, so no sentence earns its place. Brevity here comes from under-specification rather than good editing.

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?

A 5-parameter read tool with relationship includes, sparse fieldsets, no annotations, and no output schema gets nothing from this description; an agent has no idea what resource it is fetching or what the include/fields parameters will yield.

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 description coverage is 100%, so the schema already documents id, include, limit_prices, and the two sparse-fieldset parameters. The description adds no parameter meaning beyond that, which is the baseline when the schema does the heavy lifting.

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 only restates the HTTP route 'GET /v1/winBackOffers/{id}', which is already encoded in the tool name. It is effectively a tautology: it identifies the endpoint but never says what a win-back offer is or what the agent gets back.

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?

There is no when-to-use guidance, no mention of the sibling collection tool (subscriptions_win_back_offers_get_to_many_related), and no indication of when to prefer this single-instance fetch.

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