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

With no useful annotations (all hints false), the description carries the burden of side-effect disclosure, and it delivers with 'Writes nothing.' It also adds a meaningful behavioral detail: the HTML output is self-contained and needs nothing from the network, which is beyond what the schema states.

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 core purpose, then lists contents, output formats, and the critical side-effect guarantee, with every sentence earning its place.

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 two-parameter rendering tool, the description covers purpose, accepted formats, and side effects, and the schema covers parameter details. It does not specify lookup/error behavior or the exact return representation, but the Markdown/HTML wording sufficiently implies the returned content, so nothing essential 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 parameters are already well documented. The description adds only a minor reinforcement about self-contained HTML and the card-to-sign purpose, but it does not materially extend the semantic value beyond the schema.

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 and resource: render a job card for printing and client signature, including labor, materials, totals, and signature line. It clearly distinguishes itself from siblings like job_card_get, job_card_list, or job_card_create by emphasizing the print/sign-off purpose and the read-only output formats.

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 description gives a clear context for use: render a job card ready to print and hand to the client for sign-off. It does not explicitly contrast with alternatives such as job_card_get, and it lacks 'when not to use' guidance, but the intended use case is evident enough for an agent to select it.

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