ebay_get_campaign

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

Discloses return type (configuration, status, statistics) which is helpful, but does not mention side effects, permissions, rate limits, or error handling. Since no annotations exist, the description carries the burden and provides basic but not comprehensive transparency.

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?

Two concise sentences with purpose first, no extraneous words. Efficiently communicates the tool's function and return content.

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 simplicity of a single-parameter read operation, the description covers the essential aspects: what it does and what it returns. Could mention that the campaign must exist, but omission is minor. No output schema exists, so description is adequate.

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 campaignId is fully described in the schema with type and description 'Campaign ID'. The description adds no new semantic detail beyond rephrasing 'by ID', so it does not improve understanding beyond the schema.

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?

Clearly states verb 'Get', resource 'marketing campaign', and identifier 'by ID'. Specifies return contents: configuration, status, and statistics. Distinguishes from sibling tools like ebay_get_campaigns and ebay_get_campaign_by_name.

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?

Implies usage when a specific campaign ID is known, but does not explicitly mention when to use alternatives like ebay_get_campaigns or ebay_get_campaign_by_name. No guidance on prerequisites or limitations.

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