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

The readOnlyHint annotation already covers safety, and the description adds a useful limitation: individual wallet balances are not exposed. It does not mention pagination, sorting, or response format, but for a zero-parameter read-only list this is a minor gap.

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 short sentences with no wasted words. The primary action and scope are front-loaded, and the exclusion follows naturally.

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 tool with no output schema, the description conveys what the agent will get: subsidy grants and remaining pool funding, plus a clear non-goal. A bit more detail about the response shape would be helpful, but the tool is trivially invocable as described.

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 no parameters and an empty input schema, so there is no parameter burden for the description to carry. The baseline of 4 applies because there is nothing the description needs to clarify about 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 description states a clear verb and resource: 'List finite public subsidy grants and remaining pool funding.' The additional negative clause, 'Does not expose individual wallet balances,' distinguishes it from wallet/balance-related sibling tools like read_wallet.

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?

The tool's scope is clear, but the description does not explicitly state when to use it over alternatives or name a sibling tool. The 'Does not expose individual wallet balances' clause provides a boundary, but usage context is mostly implied rather than stated.

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