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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the capability boundary that this tool grants no payment or spending authority, which is genuinely useful context not present in the annotations, but says nothing about auth requirements, rate limits or the shape of the read.

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 filler, and the capability boundary is front-loaded right after the scope statement. Slightly telegraphic wording costs it nothing in size but a little in readability.

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 parameterless, read-only configuration tool with rich annotations, the description covers what is read and what authority it does not confer. Since no output schema exists, it could say a bit more about what the returned configuration contains, but the enumeration of treasury/token/wallet items largely substitutes for that.

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. The description correctly implies a parameterless configuration read and does not invent any input requirements.

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 clear read verb and enumerates what is read: treasury, token status and wallet API. It is specific enough to distinguish from siblings like read_usage or read_site_policy, though 'Base treasury' is slightly cryptic terminology.

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 when-to-use statement or named alternative among the many read_* siblings. The clause 'No payment or spending authority' does implicitly bound the tool's purpose (inspection only, not transactions), which is a partial usage cue.

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