affiliate_awin_submit_proof_of_purchase_transaction

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

With no annotations provided, the description carries the full burden. It discloses the critical read-only behavior ('without writing transactions', 'never submits live orders') and adds a notable behavioral trait: it 'Returns an activation-gated envelope', indicating conditional behavior based on activation. This exceeds a minimal safety disclosure, but it leaves the term 'activation-gated envelope' undefined and omits auth or rate-limit details.

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 concise sentences, front-loaded with the core action ('Return the current...'), followed by usage context and a behavioral guarantee. Each sentence earns its place with no redundancy or filler, making it highly efficient.

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?

Given the tool has 2 parameters, no annotations, and no output schema, the description covers the usage context and read-only/activation behavior, but it is incomplete for correct invocation: it does not explain what dryRun or advertiserId do, nor what the 'activation-gated envelope' contains. It is adequate for tool selection but insufficient for confident parameter construction.

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 schema has 0% description coverage, and the description does not explain either parameter (dryRun, advertiserId) at all. It does not clarify the purpose or expected format of these parameters, which is a significant omission given the schema provides only types. The description's read-only emphasis indirectly suggests dryRun is not for a real submission, but that does not add semantic meaning to the parameters themselves.

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 returns 'the current Awin Proof of Purchase implementation status without writing transactions', specifies the resource (Awin Proof of Purchase implementation) and distinguishes it from an actual submission tool by saying 'never submits live orders'. This is a specific verb+resource+scope statement that effectively differentiates it from the name's implication.

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 explicitly says 'Use this when a user asks about CLO or proof-of-purchase order submission and needs activation requirements', providing a clear trigger context. It also states the tool 'never submits live orders', implying when not to use it for actual submissions, though it does not name a specific alternative sibling tool.

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