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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so safety is covered; the description adds genuine context beyond that by clarifying the tool performs no side effects and instead returns screen/button/field-level instructions. It doesn't describe the shape or length of that returned guide, or whether it is tailored to a specific pledge or generic.

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 instruction is front-loaded and useful, but the opening line ('from ChatGPT, Claude or any AI agent') is marketing filler, and the closing sentence about DonorPerfect's XML API and the 'checked 23 Oct 2026' verification date is tangential to invoking this tool. Two of four sentences could be cut without losing selection-relevant meaning.

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-parameter, no-output-schema guidance tool the description covers the essential behavior, but it leaves open how the agent should convey which pledge/payment is meant and what the returned procedure looks like, which matters because the tool name implies an action it explicitly does not perform.

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, so per the baseline this is a 4. Nothing in the description needs to explain parameter meaning, and it correctly implies the caller supplies pledge context conversationally rather than through arguments.

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 (apply pledge payment) and immediately disambiguates the mechanism: it returns step-by-step DonorPerfect instructions and 'opens nothing by itself'. That distinguishes it from the cotlet_browser_* tools that actually perform the action, so an agent can tell it apart from siblings without opening a schema.

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 clear sequencing guidance: use this one for the how-to, then execute via cotlet_browser_* in the user's DonorPerfect Cloud Browser. It stops short of true when-not guidance, e.g. it never says when to prefer a direct API-style sibling like donorperfect_create_pledge or what to do if the pledge record doesn't exist.

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