get_fills

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

Notes that API credentials are required and explains the cursor-based pagination mechanism, adding behavioral detail beyond the basic read-only nature. No annotations were provided, so the description carries this burden effectively.

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?

Concise and well-structured, with no redundant wording. Each sentence serves a purpose, covering purpose, pagination, and parameter semantics efficiently.

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?

Since there is no output schema, the description explains the return shape ({ items, next_cursor }) and the meaning of each field, making the tool's behavior fully understood.

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 description adds meaning to both parameters: clarifies limit is per-page (not total) and explains cursor usage (opaque token, pass back verbatim). This goes beyond the schema descriptions.

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?

Clearly states the tool lists the authenticated account's fills (executed trades) in newest-first order, distinguishing it from related tools like get_trades or get_order_history.

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?

Provides explicit pagination instructions (continue with cursor until null) and clarifies the per-page limit behavior, though it does not explicitly contrast when to use this over alternatives.

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