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

Annotations already establish readOnlyHint=true and destructiveHint=false. The description adds meaningful behavioral context beyond that: the tool refuses until the close is signed, reads from a hash-chained file, and combines concluded figures with unproven items on one page. It does not cover edge cases such as what refusal output looks like.

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?

Three tightly written sentences front-load the deliverable, then state the refusal condition, then explain the significance of the combined output. Every sentence adds information without repetition.

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 one-parameter tool with no output schema, the description supplies the essential missing context: what the output contains, where it comes from, and the precondition for success. An agent has enough information to know when and why to call it.

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 coverage is 100% and there is only one required parameter, engagement_id, which the schema fully documents. The description adds no parameter-level detail beyond the schema baseline, so a 3 is appropriate.

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 a specific verb-resource pair, 'Deliver the engagement workpapers', and specifies the contents: certified figures plus the open-items register on one page. It also names the source, the hash-chained engagement file, making it clearly distinguishable from siblings like open_items, export, and report.

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 prerequisite and usage condition: the tool refuses until a principal has signed the close, and frames the output as the auditor-ready deliverable. It does not explicitly compare this to alternatives such as export or report, so it stops short of a 5.

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