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

Annotations already cover the read-only/idempotent/non-destructive profile, so the bar is lower. The description adds genuine behavioral context beyond them: it discloses a second return signal (whether a card is already stored) and a security/PII rule about never soliciting card details in chat.

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 first sentence is a run-on that buries the action behind a descriptive clause and an extraneous purpose aside ('so you can shop at real stores within your budget'). The operational instructions are present but not ideally front-loaded.

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?

With no output schema, the description steps in by stating both what is returned (the link) and the status flag, which is enough for an agent to call it correctly. It is essentially complete for a zero-parameter link-retrieval tool.

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 tool takes zero parameters and schema coverage is 100% (vacuously), so there is nothing for the description to compensate for. Baseline 4 applies with no parameter ambiguity.

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 makes clear this returns the owner's Agentcard Vault page link and also reports whether a card is already stored. However, it opens with a noun phrase ('The owner's own page...') that reads as a resource description rather than a verb, and it never names or contrasts itself with payment siblings like stripe_demo or pay.

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?

It gives explicit direction on when to use it ('Give the person this link') and a hard exclusion ('never ask for card details in the chat'). It stops short of naming alternative tools for related flows, so it is clear context but not full when/when-not/alternatives guidance.

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