set_page_num_ctrl

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 only indicates a mutating action ('Set'/'restart') without explaining scope, side effects, reversibility, or impact on existing page numbering.

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 concise and front-loaded with the core action, and the Args list is compact. The first line is slightly redundant with the tool name, but no information is wasted.

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 two-argument tool, the key parameters are covered and an output schema exists. However, the lack of behavioral detail and the absence of differentiation from set_page_number leave the description only minimally complete.

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 Args section adds meaning beyond the schema: doc_id is identified as coming from open_document, and page_starts_on is explained as the page number to start on. This compensates for the 0% schema description coverage, though it does not mention the default value.

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 states a specific action and resource: 'Set page numbering control — restart page number.' It clearly indicates what the tool does, but it does not differentiate it from the sibling set_page_number, so it is not fully distinctive.

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 phrase 'restart page number' implies the intended use case, and doc_id is tied to open_document, giving a prerequisite. However, there is no explicit guidance on when to use this tool versus set_page_number or related numbering tools.

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