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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so safety is covered. The description usefully adds behavioral content beyond that: it enumerates the 12 channels and states each result carries an action URL, instructions, and tax treatment. It does not mention any rate limits or freshness, but for a read-only zero-arg tool that gap is minor.

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?

Front-loaded with the org identity and the core promise, followed by a compact enumeration of channels and returned fields. Dense but every clause earns its place; no filler.

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?

There is no output schema, so the description carries the burden of describing the return payload – it does so by listing the 12 channels and the per-channel fields (URL, instructions, tax treatment). Complete enough for an agent to call and interpret the result.

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 the baseline is 4. The description correctly implies a no-argument, single-shot call ('in one response'), matching the empty input schema.

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 clear resource (all ways to give to Wounded Warriors) with specific scope: 12 named giving channels returned in one response. An agent can tell what it returns. However, it does not differentiate itself from the sibling donation_instructions_wounded_warriors, so sibling routing is left to inference.

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?

Usage is implied by 'Every way to give in one response' – call it when you want a comprehensive giving-options catalog. But there is no explicit when-to-use, no exclusions, and no naming of the related sibling donation_instructions_wounded_warriors to clarify which one applies.

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