DAO revenue

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds some genuine context beyond that: 'Live read' signals fresh, non-cached data and 'with the published USDC value' indicates the figures carry an official valuation rather than raw token amounts. It still says nothing about rate limits, defaults when no range is supplied, or pagination.

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, front-loaded with the endpoint identity and immediately followed by what the response contains. No filler. Minor ambiguity in 'and mint' — it is unclear whether mint is a dimension of the result or a separate grouping — keeps it short of a 5.

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 output schema, the description carries the burden of explaining return values, and it does sketch them: monthly revenue split by source and mint, valued in USDC. Combined with annotations that cover the read-only profile and a schema that documents two of three parameters, this is nearly complete for a simple three-optional-parameter read tool; only the default time window is unstated.

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 coverage is 67%: from and to already document the inclusive YYYY-MM range, and the description adds nothing there. It does add meaning for the undocumented segmentation parameter by framing it as 'by source', which is the one place the schema is silent. That is useful but thin, so the baseline 3 fits.

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: a read of galaxy /dao/treasury returning monthly revenue by source (segmentation) and mint with published USDC values. That is enough to separate it from treasury_balances and dao_treasury_flows, though it never names those siblings explicitly, so the differentiation is inferred rather than stated.

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 phrase 'Live read' implies when this is appropriate versus historical endpoints like treasury_history, but the description gives no explicit when-to-use, when-not-to-use, or prerequisite guidance and never points to an alternative sibling tool.

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