ebay_get_battery_qualifications

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the tool's purpose but does not reveal behavioral traits such as whether the operation is read-only, what data is returned, authentication requirements, or rate limits. The minimal description leaves agents guessing.

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 6 words. Every word is necessary; there is no redundancy. It is front-loaded with the core action and resource.

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 1 loosely-typed parameter, no output schema, and no annotations, the description is insufficiently complete. It does not explain what 'battery qualifications' are, what the response looks like, or any error scenarios. Agents lack enough context to use this tool correctly without external knowledge.

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 1 parameter 'params' with 100% schema description coverage. The description adds an example 'battery_type' which gives some context for the loose additionalProperties schema. However, the description does not explain other possible query parameters or their formats, so it adds only marginal value beyond 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 what the tool does: 'Get battery qualifications for international shipping'. It uses a specific verb+resource pattern and distinguishes this tool from siblings like ebay_get_hazardous_materials_labels or ebay_get_product_safety_labels by focusing on battery qualifications.

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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, when not to use it, or related tools. The sibling list includes many other 'get' tools for shipping compliance, but the description offers no criteria for choosing this one.

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