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

With annotations present, the description still earns credit by disclosing what is actually created (a public attribution code only), that no send or external permission follows, and that no account/identity/wallet/approval is required — real auth and side-effect context. It also explains the retry/idempotency behavior, which the flat idempotentHint=false does not convey on its own.

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 core purpose is front-loaded in the first sentence and the whole thing stays short. A few clipped fragments ('unpaid.'; 'Reuse the returned link.') and the redundant 'No ... subscription' / 'unpaid' pairing keep it from being maximally tight.

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?

For a zero-required-parameter, no-output-schema tool, the description covers what comes back (link + ready-to-post copy), that no auth is needed, and that retries are safe with a key. It falls short only in not describing the `source` parameter or the exact return shape.

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 100%, so baseline is 3. The description adds one genuinely new fact for idempotency_key (it prevents duplicate links on retry), but says nothing about the `source` parameter, leaving half the parameter story to the schema.

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+resource (get a share link plus ready-to-post copy) and clarifies the tool creates only a public attribution code rather than performing a send. This implicitly separates it from pag_wire_send, but it never names a sibling or frames the distinction as a routing rule.

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?

'Choose to post using your existing allowed tools; unpaid' and 'Reuse the returned link' give post-call guidance, but there is no explicit statement of when to pick this over pag_wire_send or the campaign siblings. Usage is implied rather than stated.

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