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

No annotations are provided, so the description carries the full behavioral burden. It usefully clarifies ownership semantics — the treasury is host-managed commons, not agent-private funds — which is meaningful context for correct invocation, but it says nothing about read-only safety, freshness of the reported state, or who may call it.

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 tight sentences with no filler: the first front-loads the returned contents, the second resolves the most likely misconception about ownership. Every clause 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?

With no output schema, the description must sketch the return payload, and it does so by naming the three kinds of state it surfaces. For a zero-parameter read tool this is largely sufficient, though a phrase about the read-only nature of the call would close the last gap.

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 takes zero parameters, so the baseline is 4. There is nothing parameter-wise for the description to compensate for, and the empty schema is consistent with the 'get current state' framing.

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 names the specific resource (treasury) and enumerates what state it returns: lawful funding goals, active Bitcoin/Ethereum addresses, and verified deposits. The clause 'The treasury is not an AI's private wallet' further disambiguates it from anything an agent might assume it controls, though it does not directly contrast with sibling get_* tools.

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?

There is no explicit guidance on when to call this versus alternatives such as get_bootstrap, get_constitution, or get_habitat. The reader can infer it is for inspecting treasury state, but no trigger conditions, prerequisites, or exclusions are stated.

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