mercury_list_treasury_statements

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

Discloses that PDF URLs are short-lived and should be fetched shortly before download. No annotations exist, so the description adds value. However, does not mention authentication requirements or rate limits, though these are implicit for a list operation.

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?

Concise with purposeful sections (USE WHEN, DO NOT USE, RETURNS). Every sentence adds value; no redundancy or fluff.

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 a single required parameter and no output schema, the description covers usage context, return structure, and constraints. Could optionally mention pagination, but not required for completeness.

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 has 100% coverage with description 'Treasury account ID' for `accountId`. The tool description adds 'Treasury account' context but does not elaborate beyond what the schema already provides. Baseline 3 is appropriate.

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?

Explicitly states 'List monthly statements for a Mercury Treasury account.' Clearly identifies the action (list) and resource (monthly Treasury statements). Distinguishes from sibling `mercury_list_statements` for deposit accounts.

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 'USE WHEN' for fetching past Treasury statement URLs for tax/audit, and 'DO NOT USE' for deposit-account statements (directs to `mercury_list_statements`) and notes IO Credit statements are not exposed.

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