etsy_payout_get

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

The description states 'Get', which is consistent with the readOnlyHint annotation. However, it provides no additional behavioral details beyond the annotation, such as authentication needs or error scenarios.

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 very concise with a single sentence, but it omits critical parameter information. It is not wasteful but is too sparse to be fully useful.

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?

Given the absence of output schema and parameter descriptions, the description fails to provide a complete picture. The tool is simple but still requires context on what a 'payout' entails and how shop_id relates.

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 0% and the description offers no explanation of the parameters (shop_id, payout_id). The agent must infer their meaning from names only, which is insufficient for correct invocation.

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 specifies 'Get a specific payout by ID', clearly indicating the action and resource. It distinguishes from similar sibling tools like etsy_payouts_list (list) and etsy_payment_get (payment). However, it does not clarify that shop_id is also required, but the input schema handles that.

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?

No guidance on when to use this tool versus alternatives such as etsy_payouts_list or etsy_payment_get. No instructions on prerequisites or context for usage.

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