ebay_get_item_by_legacy_id

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

With no annotations, the description carries full burden for behavioral context. It only states 'Get' (implying read-only) but omits details on rate limits, required permissions, or what happens if the item is not found. The required authentication parameters are not mentioned in behavior.

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 12-word sentence, very concise. It front-loads the action. However, it may be too brief, lacking structure for clarity on optional parameters. Still, it avoids fluff and earns its place.

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 tool has 6 parameters (3 required) and no output schema, the description is incomplete. It does not explain the return format, how to use variation parameters, or authentication details. Sibling tools with similar purposes are not differentiated in usage context.

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 only 17% (only legacy_item_id has a description). The description adds no new meaning to client_id, client_secret, legacy_variation_id, legacy_variation_sku, or marketplace. It merely restates that legacy_item_id is numeric, which is already in the schema.

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 clearly states the tool gets an eBay item using a legacy numeric ID, distinguishing it from siblings like ebay_get_item (likely modern ID) and ebay_search (search-based). The verb 'Get' and resource 'eBay item' with specific ID type make purpose unambiguous.

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 like ebay_get_item or ebay_search. The description does not mention prerequisites (e.g., authentication via client_id/client_secret) or provide context for optional parameters like legacy_variation_id or marketplace.

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