add_footer_textbox

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

No annotations are provided, and the description gives no insight into side effects, permissions, or behavior beyond adding a textbox. Minimal transparency for a tool that likely modifies report structure.

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 very short (one sentence), which is concise but lacks necessary details for a tool with multiple parameters. It earns a middle score for being brief but under-specified.

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 complexity of adding a textbox to a report footer (position, size, name, path), the description is inadequate. No explanation of positioning format or required properties, making it incomplete.

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 7 required parameters with only one (text) having a description. The description adds no further semantic meaning to the parameters, leaving their format and constraints unclear.

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 indicates the tool adds a textbox to the footer area, but it requires knowledge of 'add_header_textbox' to fully understand the operation. The purpose is somewhat clear but not self-contained.

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?

No guidance on when to use this tool versus alternatives like 'add_header_textbox' or 'add_body_textbox'. The description only states it's the same as the header version for the footer, without context on when which is appropriate.

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