get_shopify_payments_payouts

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only says 'Fetch', implying a read operation, but does not disclose pagination, return format, or how filters interact. The description adds no context about what a payout entails or what details are returned.

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, concise sentence with no wasted words. It is front-loaded and easily parseable. However, it is almost under-specified for a tool with six parameters, so it loses a point for lacking any structural detail beyond the bare purpose.

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 six parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what payouts are, how the query or transactionType filters behave, or what the response contains. An agent would have no idea what data to expect or how to construct an effective request.

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 fully documents all six parameters. The description adds no extra parameter semantics, leaving the agent to rely on the schema. Baseline 3 is appropriate since the schema carries the burden.

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 uses a clear verb ('Fetch') and a specific resource ('Shopify Payments payouts'), making the core purpose unambiguous. However, it does not differentiate this tool from sibling payment tools like get_shopify_payments_balance_transactions or get_shopify_payments_disputes, so the distinction relies solely on the resource name.

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?

There is no guidance on when to use this tool versus its alternatives. The description does not mention query parameters, filtering behavior, or any prerequisites. With many similar Shopify Payments siblings, this lack of direction forces the agent to infer usage from the schema alone.

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