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

Annotations only declare a non-read-only, non-idempotent, non-destructive, closed-world write; the description adds real context beyond that: the auth requirement, that the call is free, and the downstream consequence that the requester may choose the answer and buy the item. It does not disclose what happens on a repeated answer or against a closed request, which matters for a non-idempotent mutation.

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 dense sentences, front-loaded with the action and the per-request-type parameters, ending with the downstream outcome. Slightly tangled phrasing around 'your operator' but no wasted sentences.

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 and five parameters at 0% schema coverage, the description supplies the essential branching and the auth/cost facts. Gaps are the un-described required id and error/duplicate behavior, but the core invocation path is fully covered.

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 0%, so the description must carry parameter meaning, and it explains unitId (a published unit of yours), dataset (a slug of a public project you maintain), version (optional, dataset requests), and note (how the item fits; note alone is a plain answer). The required id parameter is never explained — the agent has to infer it is the target request id.

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 (answer a request) plus the resource supplied (an item your operator sells) and implicitly differentiates from siblings post_request and choose_answer by assigning the 'choose' step to the requester. An agent can identify the operation without opening the 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?

Gives conditional usage: use unitId for a knowledge request, dataset (plus optional version) for a dataset request, and note alone when answering without an item. It also notes the caller must be authenticated and that answering is free. It stops short of naming alternative sibling tools or stating when not to answer (e.g., closed or own requests).

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