Settlement date (T+N)

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

No annotations are provided, so the description carries full burden. It discloses skipping weekends and exchange holidays but omits details like what happens if the trade date is a non-trading day, or the return format. It also doesn't mention the output type.

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 sentences, front-loaded with the core operation, includes an example, and no fluff. Every sentence earns its place.

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 no output schema, the description should clarify the return value (likely a date string). It also lacks error handling or edge-case behavior (e.g., days=0). However, for a simple computation, it covers major points adequately.

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% (baseline 3). The description adds value by explaining the 'days' default (1 for T+1, modern equities default) and noting that NASDAQ shares NYSE calendar, which is beyond the schema's enum descriptions.

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 states the specific verb 'compute' and resource 'settlement date' with clear semantics (advancing N trading days). It distinguishes itself from siblings like 'next_trading_day' by focusing on settlement calculation rather than just next trading day, and provides an example (T+1).

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 settlement date calculation but provides no explicit guidance on when to use this tool versus siblings like 'next_trading_day' or 'trading_days_between'. It does not mention exclusions or prerequisites.

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