set_page_number

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

No annotations are provided, so the description must disclose behavioral traits. It indicates the tool writes to a new file but does not clarify whether the original file is modified, what permissions are needed, or any side effects. The description is too brief to fully inform the agent about the tool's 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 a single sentence that packs essential information: the action, a parameter hint, and the output context. It is concise, though the meaning of 'new file' could be made more explicit at the start.

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 tool is simple, and the description, while missing details about valid positions and whether it applies to all pages, provides enough context for basic understanding. An output schema exists, so return values need not be described. However, the lack of behavioral details and incomplete parameter info reduces completeness.

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 input schema has no descriptions, leaving all three parameters (path, out_path, position) with minimal documentation. The description adds value for the position parameter by giving an example ('BOTTOM_CENTER') and mentioning the python-hwpx library, but does not explain path or out_path. This fails to compensate for the 0% schema description coverage.

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 action ('Place page numbers') and the target resource ('to a NEW file'). It provides a specific example of the position parameter, aiding understanding. It distinguishes itself from sibling tools like set_header or set_footer.

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 by stating 'to a NEW file,' suggesting it creates a new output rather than modifying the input. However, it lacks explicit guidance on when to use this tool vs alternatives like set_header or set_footer, and does not mention prerequisites or limitations.

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