ebay_create_ad_group

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

No annotations are present, so the description carries the full burden of disclosing behavioral traits. It only mentions the API and the create action, omitting details such as idempotency, side effects, permissions, or rate limits. This lack of disclosure is a significant gap for a tool that creates a resource.

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, front-loading the main action. While efficient, it could be slightly expanded to include important context without becoming verbose.

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 absence of an output schema and annotations, the description should clarify what happens upon success (e.g., returns ad group ID) and any prerequisites (e.g., existing campaign). It misses both, leaving the agent with incomplete information. The sibling list is large but not used for 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?

The input schema has 100% description coverage, with descriptions like 'Create ad group request body' and 'campaignId required endpoint parameter'. The tool description adds no additional meaning beyond the schema, which is adequate but not enhanced. Baseline 3 is appropriate.

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 creates an ad group via the eBay Marketing API. It uses a specific verb and resource, making the purpose clear. However, it does not differentiate from sibling tools like 'ebay_get_ad_group' or 'ebay_update_ad_group', which would help an agent choose this tool.

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, nor are there any prerequisites or exclusions. The description only states the action without context, leaving the agent without decision-making support.

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