set_header_item_size

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

No annotations provided, so description carries the burden. States idempotency ('{changed: false} when nothing differs') and that missing fields are untouched. However, does not mention error behavior if the named item does not exist, which is a notable gap.

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 with no unnecessary words. Front-loaded with the main action. Every sentence earns its place.

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?

Covers the resize action, idempotency, and relationship to sibling tool. No output schema, but the description provides enough context for typical use. Could add details on parameter formats or error conditions to be fully complete.

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?

Description adds meaning for 'width' and 'height' by noting 'at least one' and 'missing fields untouched', but does not explain 'name' or 'path' parameters beyond the schema. With 0% schema description coverage, some gaps remain.

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?

Clearly states the verb 'resize' and the resource 'named item inside <PageHeader>'. Distinguishes from sibling 'set_body_item_size' by noting it mirrors it and closes a parity gap.

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 context by referencing 'set_body_item_size' and stating 'at least one of width / height'. Implicitly indicates when to use (for header items) and when not (use body variant for body items). Lacks explicit exclusions but is clear enough.

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