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

The description states 'Writes nothing,' but the annotations set readOnlyHint=false, which directly contradicts the claim: a tool that writes nothing is read-only. This is a serious inconsistency that undermines the agent's trust in both the description and the annotation. No additional behavioral context is provided beyond the format note.

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?

Four short sentences with the core purpose front-loaded. The long list of agreement sections is useful content, not fluff, and each sentence carries distinct information. Slightly dense list at the start but still efficient.

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?

No output schema exists, and the description does not explicitly state what the rendered output looks like (e.g., returned as a string, file, or URL), though the Markdown/HTML format choice implies it. The read-only contradiction also muddies side-effect understanding. Adequate for a simple two-parameter tool, but the missing return semantics and the contradiction leave gaps.

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% for both parameters: `format` already documents markdown/html and the Pro feature, while `agreement` already explains the id or client-name syntax. The description adds no parameter-specific meaning beyond this, so the baseline 3 applies.

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 opens with a specific verb and resource ('Render a service agreement') and enumerates the exact sections included, clearly distinguishing this from sibling tools that create, list, check, or update agreements. An agent can immediately tell what this tool does and what it is not.

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?

The phrase 'ready to send and sign' gives clear context for when to use the tool, and the Pro-feature note for HTML adds a practical constraint. It does not explicitly name alternatives or specify when NOT to use it, 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.