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

The annotations already declare readOnlyHint=true and idempotent, and the description reinforces rather than contradicts them by explicitly stating it "opens nothing by itself" — a valuable disclosure for a tool whose name implies a write. It also describes what the return contains (screens, buttons, fields), partially compensating for the missing output schema, though it stops short of describing format, length, or failure cases.

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?

Purpose and the crucial "does not act itself" caveat are front-loaded, and the browser hand-off follows logically. The closing sentence about DonorPerfect's XML API and lack of an official MCP server is contextual justification rather than operational guidance, so it is the one part that does not fully earn its space.

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 guidance tool with no output schema, the description covers what it returns and what to do next, which is the core need. However, it never addresses the obvious question of how pledge details (donor, amount, date) are conveyed given that the tool accepts no arguments — presumably from conversation context — and gives no indication of failure modes or prerequisites such as the user having a Cloud Browser session open.

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 schema has zero parameters, so there is nothing for the description to document and the baseline is 4. It does not confuse the agent with phantom argument references.

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 action and resource ("Create pledge in the user's own DonorPerfect account") and then clarifies the actual behavior: it returns step-by-step instructions rather than performing the write. The second sentence additionally distinguishes it from the cotlet_browser_* siblings that carry out the work, so an agent can tell what this tool does versus its neighbors.

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 — call this first to get the screens/buttons/fields, then execute with cotlet_browser_* tools — which is exactly the context an agent needs to chain it. It does not name when to prefer other DonorPerfect tools (e.g., donorperfect_apply_pledge_payment) or when this tool is unnecessary, leaving some routing ambiguity.

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