hwp_fill_fields

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

The description does not mention any behavioral traits such as whether the operation is destructive, reversible, or requires specific permissions. With no annotations, the description carries the full burden, but it only states the obvious action.

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?

Three sentences, each adding essential information: action, prerequisite, and alternatives. No superfluous content, and the main purpose 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?

The description covers prerequisite and alternatives, but lacks detail on error conditions, immediate effects, or saving behavior. Without output schema or annotations, more contextual completeness would be beneficial.

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 baseline is 3. The description adds no additional meaning to the parameters beyond the schema. The prerequisite mention is a usage guideline, not parameter semantics.

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 the tool fills values into document fields, using a specific verb and resource. It also distinguishes itself from sibling tools by providing explicit alternatives for documents without fields.

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 explicitly instructs to first use hwp_get_fields to check field names before using this tool, and provides alternative tools for when fields are absent. This gives clear when-to-use and when-not-to-use guidance.

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