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

With no annotations provided, the description carries the full burden and does so well. 'Writes nothing' explicitly rules out side effects, and 'self-contained HTML that needs nothing from the network' discloses output characteristics. It also enumerates what the rendered card contains.

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 two sentences with no filler. It front-loads the purpose, then efficiently conveys output contents, formats, network independence, and side-effect absence.

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 low-complexity tool with two parameters and no output schema, the description fully covers what the agent needs: the rendered output types, the content included, and the fact that no state changes occur. No critical invocation or outcome information is missing.

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 schema already documents the card identifier and format parameter. The description's mention of Markdown/HTML mirrors the format enum's documentation and adds no parameter-level meaning beyond it, so the baseline of 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 uses the specific verb 'Render' with the resource 'job card' and immediately scopes it to the client-facing print/sign-off use case, listing labor, materials, totals, and a signature line. This clearly distinguishes it from sibling tools like get, summary, or update.

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 intended use is clear: 'ready to print and hand to the client' tells an agent when this tool is appropriate. It does not explicitly name alternatives or exclusions, but the context is unambiguous enough for selection among the card tools.

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