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

Annotations already communicate that this is a non-readonly, non-idempotent operation caused by a write. The description adds the source restriction but does not disclose side effects such as whether the input file is left untouched, whether overwrite applies, or the one-hour download validity, which are only implied in the parameter schema.

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 core instruction is one efficient sentence that front-loads the action and use case. The trailing 'Pro.' is unnecessary and slightly weakens the otherwise lean structure.

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?

For a simple tool with four documented parameters, the description provides the missing context of when and on which documents to use it, and the schema covers the operational details. The lack of an output schema is mostly mitigated by the out_path parameter description mentioning the download link.

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 description coverage is 100%, so the baseline applies; the description does not add meaningful parameter detail beyond what the schema already documents. It merely implies the business details come from the shared profile, which is not tied to any specific parameter.

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 (put business name and VAT id in the footer) and the resource scope (every page of documents from the shared profile mcp-invoice and mcp-docx write). It is specific enough to distinguish it from generic PDF operations, though it does not explicitly differentiate it from the sibling pdf_stamp tool.

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?

It gives a clear usage context: apply before sending a document out, and only to documents created from the mcp-invoice and mcp-docx shared profile. It does not state when not to use it or mention alternatives, so it stops short of full exclusion guidance.

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