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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered. The description earns credit for disclosing the shape of the response — aggregate totals by year, outstanding amounts, and per-item epoch/date/ADA size — which is valuable because no output schema exists, though it omits pagination or ordering behavior for the list.

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?

One well-formed sentence with the resource and its contents front-loaded, no filler, and no redundant restatement of the title.

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 simple two-parameter read-only listing with no required inputs, the description covers what the tool returns and its governance context, which is the main gap an output schema would otherwise fill. The only meaningful omission is the relationship to list_governance_actions.

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?

Schema description coverage is 100% and both parameters (limit, status) are fully documented in the schema, including enum meanings. The description adds no extra semantics about filtering or limits, so the baseline 3 applies.

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 specific verb and resource ('Treasury withdrawals approved (or proposed) through Cardano governance') and enumerates the payload (yearly totals, pending amounts, per-withdrawal epoch/date/ADA size). However, it never distinguishes itself from the closest sibling list_governance_actions, so an agent must infer that this is the treasury-withdrawal subset of governance data.

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 only implied: 'totals paid out by year, what is still waiting' hints at the scope, and the status enum in the schema carries the real routing logic. There is no explicit statement of when to pick this over list_governance_actions, and no mention of the default 'paid' filter that shapes results.

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