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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing about what is produced (a formatted receipt? a URL? structured data?), what "client and server side" means operationally, or any limits — it is pure filler in a space where some output context would help.

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?

It is short, but the length comes from under-specification rather than economy; the only content-bearing token is "Receipt maker" and the rest is vendor attribution that earns no place. Not front-loaded with anything actionable.

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?

With no output schema, four parameters at 0% description coverage, and a nested line-items array, the description should carry the burden of explaining inputs and the produced artifact. It explains neither, leaving an agent unable to call this correctly.

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 0% across four parameters (merchant, lines, date, taxPct), and the description names none of them. The nested lines structure (name/qty/unitPrice) and the required-ness of merchant and lines are entirely undocumented in prose, so the description fails to compensate for the coverage gap.

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?

"Receipt maker" only restates the tool name/title (Business Receipt) without stating a specific verb or output; the appended "client and server side from freedailypro" is vendor noise, not purpose. Nothing distinguishes it from siblings like business_invoice_totals, business_pay_stub, or business_bill_of_sale_draft.

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?

No guidance on when to use this tool, when not to, or which sibling to pick instead. An agent has no basis to choose business_receipt over business_invoice_totals or business_pay_stub.

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