affiliate_awin-advertiser_propose_publisher_decision

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

Annotations include readOnlyHint=true, and the description reinforces this by stating 'it performs no network write itself.' It further discloses that the tool is experimental, emits a typed handoff, requires a human to carry it out, and returns an ApiGapResponse with no credentials. This goes well beyond the annotation and provides important behavioral context.

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 three sentences long, front-loaded with the core purpose, then providing the limitation, requirements, and return value. Every sentence adds value with no redundancy.

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 the tool's purpose, the Awin API limitation, required inputs, the fact that it performs no network writes, and the return type (ApiGapResponse with constraints, verify target, and no credentials). Given the absence of an output schema, this is a complete and self-sufficient description.

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?

With 0% schema description coverage, the description compensates by naming the required parameters (brand, programmeId, publisherId, publisherName, decision), specifying the decision enum (approve|decline), and explaining that declineReason is optional for decline. It does not expand on the meaning of each parameter, but the names are self-explanatory and the conditional relationship is clarified.

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 'prepares a guided browser handoff to approve or decline a pending publisher application,' using a specific verb and resource. It also distinguishes itself from sibling tools by explaining that Awin has no public endpoint and that this emits a handoff rather than executing the decision.

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 tool's context is clearly established: because Awin exposes no approve/decline endpoint, this is the mechanism to produce a handoff for a human to act on. It lists required parameters and the optional declineReason for decline decisions. It does not explicitly name alternative tools, but the usage scenario is unambiguous.

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