Fetch orders and refunds from the store API, incrementally from the stored cursor

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

Annotations only say readOnlyHint=false and openWorldHint=true; the description adds the crucial detail that nothing executes without confirm: true, that there is no server-side dry run, and that a request preview is returned otherwise. It stops short of describing rate limits, resumability on failure, or what the preview contains.

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 tight sentences: the operation and endpoint come first, then the write-safety caveat. No filler, and the most decision-relevant constraint (confirm gate) is front-loaded in the second sentence.

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 mutating, open-world tool with a nested body and no output schema, the description covers the safety gate but leaves gaps: what 'since' means relative to the cursor, whether the call is resumable, and what the preview response looks like.

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 coverage is 50%: confirm and idempotencyKey are already documented in the schema, and the description only reinforces the confirm gate. The 'since' field inside the nested body has no description anywhere, and the description does not explain how it interacts with the stored cursor.

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 ('Fetch orders and refunds from the store API'), the incremental cursor semantics, and even the underlying endpoint POST /v1/revenue/integrations/{id}/backfill. This clearly separates it from siblings like revenue_importCsv and revenue_listIntegrations.

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 'incrementally from the stored cursor' phrasing implies when this tool is appropriate (ongoing sync rather than a one-off import), but it never explicitly contrasts with revenue_importCsv or revenue_listIntegrations, nor does it state prerequisites such as an existing integration id.

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