핵심 요약 저장

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds important nuance: it only rewrites summaries it created, will not overwrite an unrelated same-named file, and requires replace: true to replace an existing summary. That is useful context beyond the annotations, though it still does not describe the resulting path or any failure behavior.

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 dense but front-loaded, leading with the save action and then the overwrite rule. Every clause is relevant, though the Korean sentence is somewhat packed and could be easier to scan.

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 full schema coverage and annotations, the description supplies the missing operational context: source of dir, baseline purpose for list_summary comparison, and overwrite safeguards. It is nearly complete for invocation, with only minor gaps such as how the filename scope is derived.

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%, so the baseline is 3. The description still adds real meaning by explaining why dir and instructions come from list_summary and by framing replace as a guarded overwrite switch, rather than merely repeating schema text.

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?

States a specific verb and resource: saving a summary markdown file into the course folder returned by list_summary. It also names the sibling tool it depends on, so an agent can immediately tell this is the write counterpart to list_summary.

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?

Clearly says the dir should come from list_summary output and that replace: true is only for cases with user confirmation. Usage context is strong, though it does not spell out the full when-not or alternative flow beyond the replace gate.

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