list_treasuries

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

With no annotations, the description carries full burden. It discloses the static nature of the balance field, warning against misuse for reconciliation. This is critical behavioral context. However, it omits details like default sorting, potential data freshness, or permissions required.

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 two sentences plus a warning, front-loaded with main purpose. It is efficient but the warning could be integrated. No wasted language, but the parameter descriptions in the schema are more detailed, making the description supplementary.

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 should explain response structure (e.g., pagination metadata) beyond the balance warning. It covers basic pagination and field filtering but does not clarify the summary parameter or what 'default fields' are returned.

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 100%, so parameters are already documented. The description adds 'field filtering reduces response size by 70-90%' but that is an elaboration rather than new semantics. The warning about balance refers to the response field, not input parameters.

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 clearly states 'List all treasury accounts with pagination support', identifying the specific verb (list) and resource (treasury accounts). It distinguishes itself from sibling tools like 'get_treasury' implicitly and mentions field filtering, which is a unique feature.

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 description implies usage for listing treasuries but does not explicitly state when to use this tool over alternatives (e.g., get_treasury for a single account). It provides guidance on using field filtering to reduce response size but lacks exclusions or contextual triggers.

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