hwp_insert_page_num

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

With no annotations, the description discloses insertion at cursor position and format options. However, it does not mention whether the page number is a dynamic field or static text, nor any side effects.

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 sentence with a brief second sentence about format. It is front-loaded and contains no unnecessary words.

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 simple insertion tool without output schema, the description covers the main action and parameter. It is slightly lacking in clarifying the nature of the inserted page number (field or static), but adequate overall.

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% with parameter description already provided. The tool description adds examples (e.g., - 1 -, (1)) but no significant new meaning beyond the schema.

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 'Insert page number at current cursor position' with a specific verb and resource. It distinguishes from sibling tools like hwp_insert_page_break and hwp_insert_text.

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 implies usage for inserting page numbers but lacks explicit guidance on when to use this tool versus alternatives, or any exclusions.

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