ebay_get_campaign_by_name

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

The read-only behavior is already declared by readOnlyHint=true, and the description adds only the lookup key ('by name') with no extra behavioral context such as exact-match requirements, case sensitivity, or return behavior. It is not contradictory, but it adds minimal value beyond the annotation.

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?

One sentence with the key lookup semantics front-loaded and no meaningful bloat. 'Through the eBay Marketing API' is mildly redundant given the ebay_ prefix, but it does not detract much.

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 one-parameter read-only getter, the description conveys the core call shape, but it lacks explicit distinction from nearby get/list/find campaign tools and gives no hint of response shape or edge behavior. It is adequate for invoking the tool, but incomplete for confident selection.

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 single parameter has a schema description, so the baseline is 3. The phrase 'by name' gives some semantic meaning to campaignName, but it does not explain format, exact-match semantics, or how the name maps to a unique campaign.

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?

States a clear verb ('Get') and resource ('campaign') with the lookup key 'by name', which is semantically useful and implicitly distinguishes it from id-based campaign lookups. It does not explicitly contrast with sibling tools such as ebay_get_campaign or ebay_get_campaigns, so differentiation is left to inference.

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 ebay_get_campaign, ebay_get_campaigns, ebay_find_campaign_by_ad_reference, or other campaign-related siblings. The agent must infer selection entirely from the tool name and sibling list.

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