set_header_item_position

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

With no annotations, the description handles the full burden. It discloses error conditions but does not specify behavior like idempotency, coordinate system/units, or whether it overwrites existing position. The description is adequate but not exhaustive.

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, no fluff. The action, resource, and error conditions are front-loaded. Every word contributes value.

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 4 params and no output schema, the description covers the main purpose and error cases. However, it omits parameter format details and return value expectations, which would improve completeness.

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 coverage is 0% (no property descriptions), so the description must compensate. It mentions 'top' and 'left' but does not explain their format (e.g., inches, points, string). 'path' and 'name' are not explained at all, leaving ambiguity for an agent.

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 ('move'), the resource ('existing named ReportItem inside <PageHeader>'), and the target coordinates ('top, left'). It distinguishes from sibling tools like set_header_item_size (which sets size) and add_header_item (which adds).

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?

Provides explicit error conditions: errors if no <PageHeader> (prerequisite: call set_page_header first) or no item by that name. This gives clear when-to-use and when-not-to-use guidance, including a prerequisite action.

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