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

Annotations flag this as non-read-only and destructive (destructiveHint=true), yet the description frames it purely as returning a link and never discloses what side effects or invalidation may occur — a real gap for a destructive tool. It does add useful behavioral context (idempotency in prose, the paid/cancelled guard) beyond the annotations, so it is not a contradiction, just incomplete.

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?

Front-loaded with the usage trigger followed by the return semantics and exclusion, delivered in a single dense sentence with no filler. The dash-clauses are slightly run-on but every clause carries information.

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 no explanation, and annotations carry the safety profile. However, for a destructive, one-param tool with zero schema coverage, the description leaves the order_ref format and the destructive side effects unexplained, so it is only adequate.

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 must carry parameter meaning, but it only states 'Needs the order_ref' — naming the parameter without supplying format, source, or example. It confirms requiredness but adds essentially no semantics over the bare 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?

The description states a specific verb+resource (returns the order's payable link on pinflower.cz) and clarifies that it re-serves the same link while the order is open, guarding against the 'new' in the name. It doesn't explicitly distinguish itself from a sibling like pinflower_get_order_status, which could plausibly also surface order data.

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?

Explicitly names the triggering condition ('buyer has not paid yet and the payment link expired or got lost') and the exclusion ('Not for paid or cancelled orders'), which is strong routing guidance. It stops short of 5 because no sibling alternative is named for the paid/cancelled case.

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