ebay_get_transactions

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

Beyond the readOnlyHint annotation, it discloses genuinely useful behavior: the default empty-result shape ('success status with no data when nothing matches'), the required OAuth scope, and the EU/UK Digital Signature requirement with the exact environment variables needed to sign calls. This is the kind of pre-call setup knowledge an agent cannot get from structured fields.

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?

Dense but front-loaded: purpose comes first, then filtering/paging, then edge behavior, then prerequisites. No filler sentences, though the single-paragraph run-on of filter field names is slightly harder to scan than a structured list.

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, the description covers the important gaps: empty-result semantics, time window, auth scope, and the signing prerequisite for a subset of sellers. That is enough for an agent to call it correctly without guessing.

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 the schema already documents every parameter. The description restates the filterable field names and limit/offset/sort at a high level but adds no syntax or constraint detail beyond what the schema provides, so the baseline 3 applies.

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 and resource ('List monetary transactions') and enumerates the record types returned (sales, refunds, credits, fees, transfers), which separates it from sibling finance tools like ebay_get_payouts or ebay_get_transaction_summary. The source API (eBay Finances) is named, so its scope boundary is unambiguous.

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?

Gives the operative context for calling it: five-year lookback, which fields are filterable, how to page and sort, and the required sell.finances scope. It never explicitly names an alternative (e.g., payouts vs. transaction summary) or states when not to use it, so it stops short of a 5.

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