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

With no annotations, the description carries the burden of behavioral disclosure. It adds valuable context by specifying that the brief is AI-synthesized and includes specific content sections, which goes beyond the schema. However, it does not state that this is a read-only operation, whether data is cached, or if any special permissions are needed. The disclosed content structure is positive but incomplete.

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, efficient sentence that front-loads the purpose and includes essential content details. No wasted words; it is appropriately sized for the tool's simplicity.

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 tool with one optional parameter and no output schema, the description provides sufficient information about what is returned and how the date is interpreted. It lacks explicit output schema but the content list helps. The mismatch between 'today' in the name and 'yesterday' in the description is a minor gap, but overall the description is complete enough for basic usage.

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 schema already provides full coverage for the single 'date' parameter, including format (YYYY-MM-DD) and default behavior (yesterday). The description does not add additional parameter semantics beyond what is in the schema. Per the baseline rule for high schema coverage, a 3 is appropriate.

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 the tool returns a daily brief of the Korean market for a specific date, with content components (oneLine + why + 5 points + quotes). It uses an implicit 'get' verb and identifies the resource precisely. However, it does not explicitly distinguish itself from sibling tools like get_macro_snapshot, though the Korean market focus and AI synthesis are distinctive.

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 provided on when to use this tool versus alternatives. The description only states what it does (get a daily brief), leaving the agent to infer usage context from the name. There is no mention of exclusions or complementary tools, so the agent receives no decision support.

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