insert_page_number_field

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

With no annotations, the description discloses it's a write operation and specifies the insertion point. However, it does not mention side effects, field update behavior, or return value. Additional context would be helpful.

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?

Two sentences plus an Args list, no fluff. Every part is useful and 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?

For a simple tool with one parameter and output schema, the description covers the core function and parameter. It could mention that the field displays page numbers or how to update fields after insertion, but overall adequate.

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 schema has 0% description coverage, but the description explains that para_id is the w14:paraId of the target paragraph, adding essential meaning beyond the schema's type string.

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 a PAGE field at the end of a paragraph,' specifying the verb, resource, and location. It distinguishes this tool from siblings like insert_date_field or insert_sequence_field.

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?

No guidance on when to use this tool versus alternatives like add_field or other field inserters. Prerequisites (e.g., valid paragraph) are implied but not stated.

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