add_header_textbox

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

Discloses encoding behavior and expression syntax, which adds value beyond the schema. However, without annotations, it does not cover side effects, authorization, or effects on existing items.

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 succinct sentences that are well-structured and front-loaded with the key purpose. Every sentence adds essential information with no redundancy.

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?

Despite moderate complexity (7 required parameters, no annotations), the description only fully covers one parameter. Missing details on prerequisites (e.g., editing transaction), behavior on duplicate names, and return values.

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?

Only describes the text parameter in detail; the other six parameters (top, left, name, path, width, height) lack any description, and schema coverage is only 14%.

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 ('Add') and resource ('Textbox') with a specific target ('PageHeader'). It effectively distinguishes from sibling tools like add_body_textbox and add_header_image.

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 clear guidelines on using the text parameter (static or expression, encoding handling), but lacks explicit when-not-to-use or comparisons to alternatives like set_textbox_value.

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