Add Footnote

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

Annotations provide no readOnlyHint or destructiveHint, so the description must carry the transparency burden. It only says 'Add a footnote,' which implies mutation, but does not disclose side effects, error handling, or what happens with invalid paragraph_index. Missing critical behavioral details.

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 concise with one sentence and front-loaded, but it sacrifices essential details for brevity. It is acceptably short but not optimally structured for an agent to extract all needed information quickly.

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 (many sibling tools, no output schema, no annotations), the description is incomplete. It does not explain return values, success conditions, or error scenarios. An agent would struggle to use this tool correctly without additional context.

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 has 0% description coverage, yet the description adds no parameter meaning. The properties filename, paragraph_index, and footnote_text are left completely ambiguous (e.g., path format, indexing base, text formatting). The description fails to compensate for the missing schema descriptions.

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 verb 'Add' and the resource 'footnote to a specific paragraph in a Word document,' which is specific. However, it does not differentiate from sibling tools like add_footnote_after_text or add_footnote_before_text, missing a chance to improve clarity.

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 its many siblings (e.g., add_endnote_to_document, add_footnote_enhanced). The description lacks any context about prerequisites, when not to use, or alternatives.

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