ebay_get_currencies

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

No annotations provided, so the description carries full burden. It only states 'Get currencies for a marketplace' without disclosing behavioral traits such as read-only nature, authentication requirements, rate limits, or response structure. Minimal value added beyond the tool name.

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 of four words, front-loading the essential information. It is appropriately sized for a simple tool, though a few more details on the output would not detract from conciseness.

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?

No output schema is provided, and the description does not mention what the tool returns (e.g., list of currencies, currency codes, or default currency). For a tool with one parameter and no output schema, the description should hint at the response format to fully inform the agent.

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 one required parameter 'marketplaceId' described as 'Marketplace ID'. The description does not add any additional meaning, constraints, or examples beyond the schema. Baseline score of 3 applies as schema sufficiently defines the parameter.

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 currencies for a marketplace' clearly states the action (get) and the resource (currencies) with a specific scope (marketplace). It uniquely identifies the tool among siblings, as no other tool in the sibling list is dedicated to retrieving currencies.

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 explicit guidance on when to use this tool versus alternatives. However, given the sibling list, no alternative tool provides the same functionality, so usage is implied for any scenario requiring currency information for a marketplace. Missing explicit when-not or exclusion criteria.

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