PayPing: create payment link

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description nonetheless adds genuinely new behavioral facts: the link is *permanent*, it is *public*, it creates real data, and user confirmation is required before invocation – context the annotations cannot express.

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?

Two sentences, zero filler. The effect and the return value come first, and the mutation warning sits second – correctly ordered so the agent reads capability before caution.

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 destructive, non-idempotent creation tool with no output schema, the description covers the essentials an agent needs: it warns about permanence, public exposure and confirmation. But it omits the meaning of the required `product_code`, any auth/permission requirements, and whether a created link can be revised or revoked.

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 67%, and the one parameter with no schema description is `product_code`, the only required one – the description never explains what it is, where it comes from, or its format. It also says nothing about `ask_address` or `redirect_url` behavior, so it does not compensate for the coverage gap.

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 and resource ('make a permanent public payment page for a product') and even discloses the return artifact (`url`, https://ppng.ir/d/...). This is clearly distinguishable from siblings like payping_create_invoice or payping_create_product, which create different objects.

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 gives one concrete invocation guardrail – 'confirm with the user before calling' – which is real usage guidance, but it offers no when-to-use/when-not criteria and never names an alternative (e.g. when to use create_invoice instead). Usage context is implied rather than spelled out.

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