ebay_get_advertising_eligibility

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

No annotations are provided, so the description carries the full burden. It mentions required OAuth scopes (sell.account.readonly or sell.account) which hints at a read operation, but it does not explicitly state behavior traits such as side effects, rate limits, or response details. Insufficient behavioral disclosure for a tool without 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 extremely concise—two sentences plus an OAuth line. It front-loads the primary action and is efficient with no unnecessary words.

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?

For a simple read tool with two parameters and no output schema, the description covers the essential: purpose, OAuth requirement, and parameter names. However, it lacks any mention of the return format or typical response, which would be helpful for an agent. Nearly complete.

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?

With 100% schema coverage, the baseline is 3. The description does not add extra meaning beyond the schema; it repeats parameter names without examples, defaults, or formatting tips. Minimal added value.

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 'Check the seller eligibility status for eBay advertising programs,' using a specific verb and resource. It effectively distinguishes itself from sibling tools, which are primarily CRUD operations related to ads, campaigns, etc., making the 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?

The description implies usage for checking eligibility but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention exclusions or prerequisites beyond OAuth scopes. Lacks when/why context.

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