Daily Fortune Snapshot

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

No annotations provided. Description mentions output is a score (0-100) and advice, implying a read-only operation. Does not disclose details like rate limits, authentication, or side effects, but the tool's purpose is non-destructive.

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 purpose, followed by concise input guidance. No redundant words; every sentence is necessary.

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 three parameters and no output schema, the description covers purpose, input source, and output type (score + advice). Could optionally mention response structure or error handling, but current level suffices for selection and use.

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% and schema descriptions are adequate. The description adds value by clarifying the origin of the day_master parameter (from saju_calculate/interpret) and listing valid Korean stems and English aliases, which aids correct invocation.

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?

Title and description clearly state the tool returns a daily fortune score and advice based on Day Master and date. It is distinct from sibling tools (saju_calculate, saju_interpret, saju_compatibility) which handle calculation, interpretation, or compatibility.

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?

Explicitly instructs users to obtain the Day Master from prior saju_calculate or saju_interpret calls and provides valid input formats (Korean stem or English alias). Missing explicit when-not-to-use instructions but context is clear enough.

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