set_page_footer

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

With no annotations, the description must fully disclose behavior. It only references set_page_header without any details about side effects, permissions, or consequences of using the tool. The agent receives no insight into what changes occur or what requirements exist.

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 extremely short but at the expense of completeness. It is not self-contained and relies on another tool's description. There is no structure or progressive disclosure; it is a single vague sentence.

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 has 4 parameters, no annotations, no output schema, and a complex set of sibling tools, the description is far from complete. It fails to provide essential context for correct usage, making it inadequate for an AI agent to reliably invoke.

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 description provides no information about the parameters. Schema coverage is 0%, meaning the description adds no meaning beyond the schema itself. The agent must infer the purpose of path, height, print_on_first_page, and print_on_last_page without any contextual help.

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 states the tool is equivalent to set_page_header but for PageFooter, which implies it sets properties on a page footer. While it relies on understanding set_page_header, the object is clearly identified, and it distinguishes from siblings by analogy.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or scenarios where this tool is appropriate or not. The description is too brief to offer usage guidance.

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