get_day_quality

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

No annotations are provided, so the description carries the full burden. It mentions 'Instant calculation' which implies speed, but does not disclose any limitations, side effects, or auth requirements. For a simple read tool, this is adequate but lacks depth.

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 very concise: two brief lines explaining purpose and constraints, followed by a structured Args section. Every sentence adds value and is 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 the tool has only one parameter and an output schema exists (context signal), the description adequately explains what the tool returns (day quality indicators) and the input format. It is sufficiently complete for a simple lookup tool.

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 includes an Args section with the date parameter described as 'ISO 8601 date, e.g. '2026-04-10''. The schema has one required date string property with no format info, so the description adds meaningful format and example guidance.

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 it gets Tong Shu day quality indicators, naming specific indicators (Day Officer, 28 Constellation, Flying Star). This is a specific verb+resource and distinguishes from siblings like get_daily_pillars or get_daily_interactions.

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?

It says 'No natal chart needed. Instant calculation.' which guides the user that this tool is appropriate for quick day quality queries without additional context. While it doesn't explicitly state when not to use, it provides useful context for when to use it.

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