mhlb_print_transaction

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

Annotations already set readOnlyHint=false and openWorldHint=true, indicating possible side effects. The description adds useful context that the endpoint renders the passed record rather than performing a lookup, but it does not explicitly disclose the default file-writing behavior (though the inline parameter description covers it). This is acceptable given annotations shoulder the side-effect burden.

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?

Two concise sentences with the primary purpose first, followed by a crucial behavioral nuance. Every word adds value, and there is no redundancy or filler.

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?

The description captures the core purpose, the source of the transaction object, and the non-lookup behavior. It does not explicitly state the default file-writing side effect or the exact return format when inline is false, but these are covered in the parameter schema. Given no output schema and moderate complexity, this is adequate and largely complete.

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 parameters are already well-documented. The description reinforces that the transaction object should come from mhlb_get_transaction, which matches the schema but does not add new meaning beyond that. No additional parameter semantics are introduced by the description itself.

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 clear verb+resource: 'Generate the printable receipt PDF for one transaction.' It distinguishes from sibling print tools by naming the resource (transaction) and clarifies that it renders an existing record rather than looking one up by id, which sets it apart from mhlb_get_transaction-like tools.

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 explicitly instructs to 'Pass the transaction object from mhlb_get_transaction' and notes that it does not look up by id, giving a clear prerequisite and preventing misuse. However, it does not explicitly name sibling print tools (e.g., mhlb_print_calendar, mhlb_print_orders) or state when not to use those, so the guidance is strong but not fully exhaustive.

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