ebay_get_return_policies

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

The description only indicates a read operation ('Get'), which is insufficient given the absence of annotations. It does not disclose authentication requirements, rate limits, or what the returned data encompasses beyond the parameter.

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, clear sentence that is appropriately concise. It is front-loaded and wastes no words, though it could benefit from slight expansion.

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 1 parameter and no output schema, the description lacks completeness. It does not describe the expected return value (e.g., list of return policies) or any additional context needed for correct invocation.

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 100% with the single 'marketplaceId' parameter fully described in the schema. The description adds no semantic value beyond the schema, so it meets the baseline but does not enhance understanding.

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 'Get return policies for the seller' clearly states the verb and resource, distinguishing it from sibling tools like 'ebay_get_return_policy' (singular) and 'ebay_get_return_policy_by_name'. However, it could be more explicit about returning all policies for the seller's account.

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 is provided on when to use this tool versus alternatives such as 'ebay_get_return_policy' or 'ebay_get_return_policy_by_name'. There is no mention of prerequisites or context for use.

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