ebay_get_ad

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

With no annotations, the description does not disclose behavioral traits beyond the 'get' verb. Missing details such as read-only nature, required permissions, error handling (e.g., item not found), or output format.

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?

Single sentence, very concise. However, it may be too terse given the lack of other context. Could include a brief note on output or usage without becoming bloated.

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 complexity of the sibling set, lack of output schema, and absent annotations, the description is insufficient. It does not specify return values, possible errors, or how the tool fits into the ad management workflow.

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 basic descriptions, but the description adds no additional semantic meaning. It does not explain how to obtain adId or campaignId, or their significance in the overall workflow.

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 states 'Get ad' which clearly identifies the action and resource. It distinguishes from plural variants (ebay_get_ads) by implying singular retrieval, but does not specify the ad type (e.g., Promoted Listings) or context.

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 on when to use this tool versus alternatives. Among many sibling tools (ebay_get_ads, ebay_get_ad_group, ebay_create_ad), the description provides no context for selection, prerequisites, or fallback options.

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