get_trading_days

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is clear. The description adds behavioral constraints (market must be CN/HK/US, dates YYYY-MM-DD) and implies a read-only lookup, consistent with annotations. No contradiction.

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 well-structured with comments, strategy, critical rules, examples, and an 'Args' section. However, the 'Args' section largely duplicates the parameter descriptions, making it slightly redundant. Still, it is clear and front-loaded.

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 that an output schema exists (though not shown in full), the description need not explain return values. The description covers all necessary aspects: purpose, valid inputs, and usage strategy. It is complete for a parameter-rich tool with high annotation coverage.

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 0%, so the description must fully explain parameters. It does: market as 'Market code: CN / HK / US', start as 'Start date YYYY-MM-DD', end as 'End date YYYY-MM-DD'. This adds meaning beyond the raw schema, but could be improved by explicitly listing allowed values for market.

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 'Get trading days for a market between dates.' This is a specific verb+resource combination that distinguishes it from siblings like 'get_quote' or 'get_candlesticks' which return different financial data.

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 includes a <strategy> section that tells the AI to directly invoke with market and date range, <critical_rules> specifying valid market codes and date format, and an <examples> section showing exact usage. This provides comprehensive guidance on when and how to use the tool.

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