Market hours

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

While annotations (readOnlyHint=true, openWorldHint=true) already indicate a safe read operation, the description adds no behavioral context beyond stating it provides a schedule. There is no mention of timezone handling, holiday schedules, or return format, which would be useful for a trading-hours tool.

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 a single, clear sentence with no unnecessary words. It is well-structured and front-loaded with the core purpose.

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?

For a simple tool with one parameter and annotations present, the description is minimally adequate. However, it could mention that the output is likely a list of day/time objects, and it lacks completeness regarding what exactly is returned.

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 input schema has 100% coverage with a single parameter 'market' described with examples. The description adds no additional meaning beyond the schema. Baseline score of 3 is appropriate as the schema already does the job.

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 that the tool returns the weekly trading-hours schedule for a market. The verb is implicit but the resource and scope are well-defined. It effectively distinguishes from siblings like 'markets_status' which likely gives current status rather than schedule.

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?

No guidance is given on when to use this tool versus alternatives such as 'markets_calendar' or 'markets_status'. The description does not mention any exclusions or prerequisites, leaving the agent to infer the appropriate context.

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