etsy_receipt_get

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

Annotations declare readOnlyHint=true, and the description 'Get' aligns with that. However, beyond the annotation, the description adds no extra behavioral context such as required permissions, error conditions, or consequences. It does not contradict annotations.

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 sentence with no extra words, achieving conciseness. However, it is overly brief and sacrifices clarity and completeness for brevity, which is not ideal for a helpful tool definition.

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 two required parameters, no output schema, and no parameter descriptions, the description is insufficient. It does not explain what a receipt is, what data is returned, or how this tool fits within the wider Etsy API context (e.g., needing a shop_id and receipt_id from earlier calls).

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 input schema has 0% description coverage for its two required parameters (shop_id and receipt_id). The description only mentions 'by ID' but does not explain either parameter's meaning, format, or relationship. It fails to compensate for the lacking 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?

The description states 'Get a single receipt by ID', which clearly identifies the action and resource. It is specific but does not differentiate from siblings like etsy_receipts_list, etsy_receipt_update, or etsy_receipt_transaction_get, which could cause confusion for an agent.

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. For example, it does not state that this tool should be used for fetching a specific receipt, while etsy_receipts_list is for multiple receipts. The description offers no context for its appropriate use.

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