Add Footnote Robust

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

Mentions robust validation and error handling but lacks specifics on behavior like error outcomes, idempotency, or side effects. No annotations beyond title.

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?

Very concise (two sentences) but sacrifices clarity and completeness; could add more value without becoming verbose.

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?

Inadequate for a tool with 6 parameters and no output schema. No mention of required filename, location selection, or results. Relies entirely on schema names.

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?

With 0% schema description coverage, description adds no explanation for any of the 6 parameters, leaving the agent without insight into how to properly set search_text, paragraph_index, etc.

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?

Description clearly states verb 'add' and resource 'footnote', with emphasis on robust validation and Word compliance. However, it doesn't distinguish from sibling tools like add_footnote_enhanced or add_footnote_to_document.

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?

Implies it's production-ready but provides no explicit guidance on when to use this vs. alternatives, nor when not to use it.

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