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

With no annotations provided, the description carries the behavioral disclosure burden. It clearly signals a read-style operation ('Return') and adds meaningful context via 'content-blind aggregate,' but it does not disclose data freshness, access restrictions, or any side effects, which are less critical here given the zero-parameter read nature.

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?

The description is a single, front-loaded sentence with no filler or redundancy. It immediately states the action and the key qualifier ('content-blind aggregate'), then names the return value. Every word earns its place.

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, no-output-schema tool, the description is largely complete: it states what is returned and the key aggregating behavior. The only minor gap is that 'constitutional split' is not elaborated, but this is likely domain-specific terminology rather than a missing operational requirement.

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 accepts zero parameters and the schema documents this fully with 100% coverage. There are no parameters whose semantics need explanation, so the description does not need to compensate for any schema gaps.

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 ('Return') and names a concrete resource: content-blind aggregate Treasury totals and the constitutional split. It is clear and distinguishes this tool from the 'discover' siblings by emphasizing 'content-blind aggregate,' though it does not name those alternatives explicitly.

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 purpose strongly implies when to use it: when aggregate Treasury totals and the constitutional split are needed. However, there is no explicit guidance about when not to use it or which sibling tools should be preferred for content-aware discovery or admission-related queries.

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