get_last_trading_day

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

No annotations exist, so weight falls on description. It only states it gets 'latest' info and returns a Markdown table, without disclosing read-only nature, potential delays, or market scope.

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 with an example, efficiently conveying core purpose and output format. The example is slightly redundant due to zero parameters but not harmful.

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 parameters and an output schema, the description is adequate but lacks specifics like which exchange's calendar, date formats, or whether historical data is included.

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?

Input schema has zero parameters with 100% coverage. The description adds value by stating the output is a Markdown table containing recent trading day info, which goes beyond the empty schema.

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 it retrieves the latest trading calendar info including trading days and holidays, which clearly defines the verb and resource. The tool is distinct from siblings focusing on stock data or financial analysis.

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?

Only an example call is provided; no guidance on when to use this tool versus alternatives like get_current_count_changes or get_real_time_data.

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