ebay_get_email_campaigns

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

No annotations are provided, and the description does not disclose key behaviors such as pagination (implied by limit/offset parameters), rate limits, or whether it returns all campaigns or only a subset. The tool name and description only convey basic retrieval.

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 that states the purpose without extraneous words. However, it is too brief to provide adequate context, sacrificing completeness for brevity.

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 the presence of four optional parameters, the description is insufficient. It does not explain the return format, pagination behavior, or how this tool differs from similar sibling tools like 'ebay_get_email_campaign' or 'ebay_get_promotions'.

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?

Although the input schema has 100% description coverage, each parameter is described generically (e.g., 'q optional endpoint parameter') without adding meaning beyond the name. The tool description does not explain how parameters affect the query, such as valid values for 'sort' or the role of pagination.

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 verb ('Get') and resource ('email campaigns'), and the name implies a list operation. However, it does not explicitly differentiate from the sibling 'ebay_get_email_campaign', which likely retrieves a single campaign.

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 like 'ebay_get_email_campaign' or other listing tools. The description does not specify use cases or prerequisites.

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