List Deposits

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds a valuable behavioral constraint: at least one of booking_id or since_utc is required to keep results bounded, which is not stated in the schema and is important for correct invocation.

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 a single sentence with a clear verb-first structure, a parenthetical clarification, and a concise constraint. Every phrase contributes meaning, with no redundant or filler content.

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 list tool with three scalar parameters and no output schema, the description covers the core purpose, the key parameter-selection logic, and the boundedness constraint. It does not describe return format or pagination, but given the tool's simplicity, this is acceptable and mostly 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?

The input schema documents since_utc and booking_id (67% coverage), so the baseline is 3. The description adds the relationship between these two parameters and the requirement to provide one, which aids agent understanding. However, the 'limit' parameter's semantics remain unexplained beyond its type.

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 'List deposits (payouts grouping)' with a specific verb and resource. It clarifies the domain as payout groupings, which helps differentiate it from sibling tools like ownerrez_list_payments and ownerrez_list_refunds, though it does not explicitly name alternatives.

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 provides clear parameter-usage context: 'Provide booking_id (for one booking) or since_utc (recent activity) — one is required to keep results bounded.' However, it does not mention when to choose this tool over sibling tools or any exclusions, so usage guidance is only partially complete.

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