Create a new receipt

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

Annotations already indicate readOnlyHint=false, so the mutation nature is known. The description adds no extra behavioral details such as required permissions, side effects, or rate limits. It doesn't contradict annotations, so the baseline of 3 applies.

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 contains a redundant duplicate sentence ('Create a new receipt.') that provides no additional value. While short, the repetition is unnecessary and wastes space.

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?

Given the tool has a nested body schema and many sibling tools, the description provides almost no context beyond the endpoint. No information about required vs optional fields, example usage, or when to choose this over related create tools. The agent must infer everything from the schema.

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?

The schema provides detailed descriptions for all properties inside the body object, even though the top-level body parameter lacks a direct description. The tool description itself adds no parameter guidance, but the schema's coverage is sufficient enough to not be a major gap. With 50% formal coverage, the description does not compensate, but the schema carries the weight.

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 clearly states the action 'Create a new receipt' with a specific verb and resource, and includes the endpoint for reference. However, it does not distinguish this tool from siblings like create_purchase_invoice or create_sales_invoice, so it doesn't fully earn a 5.

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?

There is no guidance on when to use this tool versus alternatives. The description merely repeats the tool's name and endpoint, offering no context about scenarios, prerequisites, or exclusions.

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