set_page_number

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It clearly implies a mutation by inserting a control, but it does not state where the control is inserted, whether existing page numbers are replaced, or what side effects might occur. This is a significant gap for a document-modifying tool.

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 clear sentence with no wasted words, so it is concise. However, it is so sparse that it omits essential context about parameters and behavior, making it under-specified rather than efficiently complete.

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 tool with four parameters and zero schema description coverage, this description is not sufficient for correct invocation. The output schema exists, so return-value details are not needed, but the description still fails to convey parameter semantics, insertion behavior, or when to use this tool over related siblings.

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 description coverage is 0%, so the description must compensate for the undocumented parameters, but it does not. It never explains what 'format', 'position', or 'start_number' mean, what values they accept, or how they affect the inserted page number control. The agent is left guessing about all four parameters.

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 identifies a specific action, 'Insert', and a specific resource, 'page number control', making the basic purpose clear. However, it does not distinguish this tool from siblings like set_page_num_ctrl or insert_auto_number, which may serve similar or overlapping purposes.

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?

There is no guidance on when to use this tool versus alternatives such as set_page_num_ctrl or insert_auto_number. The description does not mention prerequisites, document context, or any scenario where this tool is preferred, leaving usage entirely to inference.

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