resize_page

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

The description does not disclose essential behavioral traits such as how content on the page is affected (scaled, cropped, etc.), whether the operation is reversible, or if specific permissions are needed. With no annotations, the description carries full burden but fails to provide this context.

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, which is concise but overly terse. It could be expanded with additional context without becoming verbose.

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?

Given the tool has 6 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain the behavior of resizeMethod, anchorPoint, or coordinateSpace, nor the effect on page content. A resize operation typically requires more detail to use correctly.

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 covers only 50% of parameters with descriptions (pageIndex, width, height). The descriptions are minimal ('Page index', 'New width in mm'). The enumeration parameters (resizeMethod, anchorPoint, coordinateSpace) lack descriptions in the schema, and the tool description does not explain them. Thus, the description adds little value beyond what is already in 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 'Resize a page' clearly states the verb and resource. It distinguishes from sibling tool 'resize_page_item' by naming the target as a page, not an item. However, it lacks explicit differentiation from other page-related tools like 'set_page_properties'.

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 is provided on when to use this tool versus alternatives like 'resize_page_item' or 'set_page_properties'. There is no mention of prerequisites or typical use cases.

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