resize_page

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 only states 'Resize a page' without mentioning side effects (e.g., content scaling, page item repositioning), required permissions, or limitations. The enumeration fields in the schema hint at behavior, but the description itself lacks transparency.

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 extremely short (one sentence), which is concise but lacks structure and detail. It does not front-load important information; it is merely a phrase. While not verbose, it could benefit from additional context without becoming overly long.

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 incomplete. It does not explain return values, prerequisites, edge cases (e.g., min/max dimensions), or the effect of different resize methods. Much essential context is missing.

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 only 50% per context signals, meaning half the parameters lack descriptions in the schema. The tool description does not include any parameter information, thus failing to compensate. Even with some schema descriptions, the description adds no 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 'Resize a page' clearly identifies the action on a specific resource (page). It distinguishes from sibling tools like 'resize_page_item' which targets page items, and 'set_page_properties' which may cover other attributes. However, it does not elaborate on what resizing entails (e.g., changing dimensions, scaling content), leaving some ambiguity.

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 provides no guidance on when to use this tool versus alternatives such as 'set_page_properties' or 'reframe_page'. There are no context or prerequisite notes, nor any exclusion criteria.

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