set_page_header

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

No annotations provided, so description must disclose behavior. It mentions 'create or update' and partial writes, but omits potential side effects, error conditions, permissions, or idempotency. Inadequate for a mutation tool.

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 short sentences with no redundancy. Information is front-loaded and every word adds 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?

Missing output schema and low schema coverage. Description does not cover return value, error handling, or prerequisites (e.g., report must be in edit mode). Incomplete for a mutation tool with no annotations.

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%, yet description only lists field names ('height plus PrintOnFirstPage / PrintOnLastPage flags') without adding meaning, types, or constraints. Does not explain how path works or what values height accepts.

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 'create or update' and the resource 'PageHeader', specifying the fields affected (height, PrintOnFirstPage, PrintOnLastPage). Distinguishes from sibling tools like set_page_footer by targeting the header specifically.

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?

Implies usage for modifying page header, but does not explicitly compare to alternatives (e.g., set_page_footer, add_header_image). The phrase 'only what's passed gets written' hints at partial updates but lacks when-to-use guidance.

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