ebay_get_ad_group

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

The readOnlyHint annotation already covers the safety profile, and 'Get' is consistent with a read-only operation. The description adds no behavioral context such as return contents, authorization needs, or rate limits, but it does not contradict the 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 a single short, front-loaded sentence. 'Through the eBay Marketing API' is mildly redundant given the tool name, but it is low-cost and does not add meaningful clutter.

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-only retrieval with two clearly named parameters, the description is minimally adequate. It lacks return-value context and does not clarify when to use this over related ad-group tools, but the schema and annotations cover the essential mechanical details.

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 100%, so the baseline is 3. However, the schema descriptions are tautological ('adGroupId required endpoint parameter', 'campaignId required endpoint parameter'), and the tool description adds no additional meaning beyond the parameter names.

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 operation ('Get ad group') and the API context ('eBay Marketing API'). It does not explicitly distinguish itself from similar siblings like ebay_get_ad_groups or ebay_get_ad, so it stops short of full differentiation.

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?

There is no guidance on when to use this tool, what prerequisites exist, or which alternatives might be more appropriate. An agent cannot tell from the description whether this is the right call versus related campaign/ad-group tools.

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