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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'opens nothing by itself,' which is the key behavioral fact an agent needs. It also discloses the shape of the response (step-by-step screens, buttons, fields), something the annotations cannot convey, though the trailing note about DonorPerfect's XML API adds background rather than operative behavior.

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 operative content (returns steps, opens nothing, then use cotlet_browser_*) is stated early and clearly, but the leading sentence about sending from 'ChatGPT, Claude or any AI agent' is marketing framing that misdirects, and the final sentence about the XML API and absence of an MCP server is background that does not help invocation.

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 parameters, no output schema, and full annotation coverage, the description supplies what is otherwise missing: what the tool returns and that a separate browser tool family completes the action. Only the unaddressed question of what the steps look like or whether they are account-specific keeps it below complete.

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 there is nothing for the description to disambiguate. It correctly implies a no-input invocation by describing the output directly rather than any inputs.

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 first sentence claims the tool will 'Send thank-you email in the user's own DonorPerfect account,' but the second sentence reveals it only 'Returns how to do it in DonorPerfect step by step (screens, buttons, fields) and opens nothing by itself.' The real function (return instructions, not perform the send) is stated, but only after a headline that points the opposite way, so an agent skimming could misjudge the tool.

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 routes the agent onward: after getting the steps, 'do it with the cotlet_browser_* tools in the user's DonorPerfect Cloud Browser,' which names the alternative tool family and the condition for using it. It does not state when this guidance tool should be skipped in favor of the direct donorperfect_* write tools, so it stops short of full when/when-not coverage.

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