resize_page_item

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It merely states the obvious operation without explaining effects like how the anchor point influences resizing, whether changes are immediate, or if there are constraints (e.g., minimum size). This is insufficient for an agent to understand the tool's behavior.

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, short sentence with no extraneous words. It is as concise as possible while still conveying the basic purpose.

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 5 parameters (including an enum for anchor point) and no output schema, the description is overly minimal. It does not explain the anchor point behavior, return values, or any side effects, leaving the agent with insufficient context for proper usage.

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 already has 100% description coverage for all 5 parameters, so the baseline is 3. The description adds no additional meaning beyond what the schema provides, failing to elaborate on the relationship between parameters or the impact of the anchor point enum.

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 the action 'Resize' and the resource 'page item', which is a specific verb+resource combination. However, among many sibling tools that also operate on page items (e.g., move_page_item, delete_page_item), it does not provide any additional context to differentiate itself beyond the verb.

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 like set_page_item_properties, which could also modify dimensions. There is no mention of prerequisites, such as needing the page item to be selected or the page to be active.

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