Get Jumbo Order Deposits

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

The readOnlyHint annotation already declares this is a safe read operation. The description adds useful context beyond that by specifying the returned data categories and the order-scoped nature of the query. It does not contradict the annotation and does not need to disclose mutation or auth behavior.

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 tightly written sentences with no filler. The purpose and required parameter are front-loaded, and the order-scoped constraint is stated immediately after, so the agent gets the essential information first.

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 simple single-parameter read tool with annotations covering safety and a fully documented schema, the description is complete. It even names the return contents despite there being no output schema, so an agent knows what kind of deposit data to expect.

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%, and the single order_id parameter is already documented as required in the schema. The description reinforces that requirement and adds the rationale that the query is order-scoped, but it does not add syntax, format, or value constraints beyond what the schema provides.

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?

States a specific verb (Read), resource (statiegeld/deposit information), and scope (for one order), and names the return contents: deposit catalogue, returned deposits, and returned total. An agent can distinguish it from sibling tools like jumbo_get_balance or jumbo_get_stamps without opening the schema.

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 establishes a clear prerequisite (requires an order_id) and explains that the query is order-scoped. However, it does not name alternatives or state when-not to use it versus related receipt or balance tools, leaving usage context implied rather than explicit.

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