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

With no annotations, the description fully discloses behavioral traits: data is aggregated from daily snapshots before purge, never deleted, cached for 5 minutes, rate-limited, and requires no authentication. This provides clear expectations for an AI agent.

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 concise, well-structured, and front-loaded with the core purpose. Every sentence adds value, listing fields and usage constraints without redundancy.

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?

Given zero parameters and no output schema, the description covers all necessary context: data source (daily snapshots), aggregation (monthly), permanence, field list, authentication, rate limits, and caching. It is fully sufficient for an agent to use this tool.

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 input schema has zero parameters, so baseline is 4 per guidelines. The description adds no parameter info, which is appropriate as none exist.

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?

Description clearly states the tool returns a permanent monthly archive of stablecoin flow data, one row per month, aggregated from daily snapshots. It explicitly mentions the verb 'Returns' and resource 'permanent monthly archive', and distinguishes from likely real-time or daily tools by emphasizing permanence and long-term macro context.

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?

Provides usage details like no authentication, 60 req/min rate limit, and 5-min cache. However, it does not explicitly guide when to use this tool versus siblings such as stablecoin_flows or stablecoin_history, limiting differentiation guidance.

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