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

The description discloses the paid nature ($0.01 USDC on Base) and the payTo address, as well as the 366-day cap and holiday coverage. It does not explicitly state read-only behavior, but the annotations provide readOnlyHint. Payment details are transparent, but side effects like the payment process are not fully explained.

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 and structured as a single statement with key details embedded. It avoids unnecessary verbosity but is somewhat dense, packing multiple facts into one sentence.

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?

The description covers payment, calendar scope, and parameter constraints, but lacks explicit information about the output format or how the payment is executed. Given the tool's complexity (paid and blockchain-related), the description is not fully complete but covers essential operational aspects.

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 description explains the usage of date, start, and end parameters, including defaults and caps. It does not mention the tz parameter, but the schema provides its description. Overall, parameter semantics are well-covered.

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 indicates this tool provides US federal business-day calendar information, mentioning holidays and weekday rules. However, it does not explicitly state the exact output (e.g., count, boolean, or list), so the purpose is clear but not fully specified.

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 provides no guidance on when to use this tool versus the sibling tools. There is no mention of alternative use cases or comparative advantages, leaving the user without context for selection.

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