delete_header

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely states the operation without any details on side effects, permissions, error conditions, or the scope of deletion (e.g., entire header section vs. specific content).

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 concise sentence with no filler words, perfectly efficient for the information it conveys.

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's simplicity (one optional parameter, output schema present), the description is near-minimally complete but lacks clarity on the meaning of location values and does not mention what happens if the specified header does not exist. The output schema existence reduces the need to describe return values, but behavioral context is still thin.

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 input schema has 0% description coverage, but the description lists three possible values for the location parameter (default, first, even), adding meaning beyond the schema. However, it does not explain what each location refers to (e.g., first page, odd/even pages), leaving ambiguity.

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 (delete) and the resource (header), and specifies the location parameter with three options: default, first, or even. However, the term 'even' might be ambiguous (odd/even pages) and there is no differentiation from sibling delete tools like delete_footer, though the resource name distinguishes them.

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 edit_header_footer or delete_footer. It does not mention prerequisites, conditions, or scenarios where this tool is appropriate.

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