시공 체크리스트

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

The annotations already declare readOnlyHint and idempotentHint, so the read-only nature is covered. The description adds meaningful behavioral context: phase definitions, item counts, and the fact that the process parameter groups during-phase checks by process, plus the implicit return of a checklist rather than an action. It does not contradict the annotations.

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 dense sentence plus an example-clause sentence. It is front-loaded with the tool name and scope, packs a lot of information into few words, and avoids filler, though a slight restructuring could make the phase rules even 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 this is a simple read-only checklist lookup with two parameters and no nested/output schema, the description is complete enough for an agent to know how and when to call it. The only minor gap is that it doesn't explicitly describe the shape of the returned checklist, but the contextual signal (no output schema) makes that less crucial.

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 the schema already explains phase and process parameters. The description adds extra semantic info such as the breakdown of 36/22/22 items per phase and the examples of process values (mok, lock, tile, wallpaper). This goes beyond the ordinary schema descriptions without being redundant.

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 identifies the tool as a construction checklist for the inner door, breaking it down into three phases (pre, during, post) with concrete item counts, and gives example queries that map to user intents. This separates it from sibling tools like the process guide, cost reference, and FAQ search.

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?

The description gives explicit examples of when to use the tool: 'What should I prepare before construction', 'What to check when working', and 'inspection before move-in'. It clearly covers common use cases, though it does not explicitly name sibling tools to exclude, so it lacks a full 'when not to use' statement.

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