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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, establishing a safe read operation. The description adds behavior beyond annotations by specifying the data scope and fields returned, including the status of the money collection. No contradictions.

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?

Two focused sentences: the first front-loads the exact return payload, the second gives the user context for invocation. Every word earns its place; no repetition of schema or annotations.

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, read-only list tool with rich annotations, the description fully covers what the agent needs: what data is returned and when to call it. Sibling similarity is handled through the explicit usage scenario; the lack of an output schema is compensated by enumerating the returned fields.

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 has zero parameters and the schema coverage is 100% (empty object). As the baseline for no parameters is 4, and the description correctly implies no input is needed, there is nothing more to explain.

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 uses a specific verb ('Zwraca' – returns) and identifies the exact resource ('otwarte petycje stowarzyszenia') plus the returned fields (name, addressee, page URL, collection status). It also distinguishes the tool's use case from sibling tools by stating it is for donors asking what to support.

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 gives two concrete usage conditions: when a donor asks what they can donate to, or wants to support a specific cause. It does not name sibling tools or state when not to use this tool, but the provided conditions are clear and sufficient for selection.

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