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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety/mutation profile is covered. The description adds genuine value by disclosing routing logic per banner card status (unclaimed→referral, claimed→retailer media team, registered→agent-to-agent), which is real behavioral context beyond the annotations, though it omits idempotency implications and side effects.

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 short but stylized rather than front-loaded: the leading colon-fragment and the cryptic closer 'Settles at the door' spend words without conveying actionable meaning, so it is under-specified rather than genuinely concise.

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?

An output schema exists, so return values need not be described, but for a 9-parameter, 7-required mutation tool the description leaves too much implicit: several parameters, the meaning of the optional note/decision_id, and the practical effect of a successful submission are all unaddressed.

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 0% across 9 parameters, so the description must compensate. It names maker, budget, GTINs, market and banners (with the useful constraint that budget is 'a person approved'), but leaves budget_approved_by, contact, note and decision_id entirely unexplained in both schema and description.

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 enumerates the packet contents (maker, approved budget, GTINs, market, banners) and states the routing outcome, so the gist of submitting a demand is recoverable. But the operative verb is metaphorical ('Hand off: the packet') and phrases like 'Settles at the door' obscure rather than clarify what the tool actually does, so it stops short of a clean verb+resource statement.

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 clause 'or a gap naming what is missing' hints that a partial packet yields a validation-style gap response, which is useful. However, there is no guidance on when to call this versus siblings like a2a_handoff, receive_demand, quote_package, or gate_transaction, and no stated prerequisites.

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