ebay_get_keywords

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

With no annotations provided, the description carries full burden for behavioral disclosure. It lacks information on read-only nature, authentication requirements, rate limits, or pagination behavior. The term 'all keywords' could be misleading given pagination controls.

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 extremely concise at one sentence, front-loading the core purpose. However, it could include a brief note on pagination or filtering 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 tool's four parameters including pagination and filtering, and no output schema, the description is too minimal. It omits details about return structure, pagination behavior, and parameter combinations, leaving significant gaps for an agent.

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 baseline is 3. The description adds no parameter information beyond the schema, but since the schema already describes each parameter adequately, the description's lack of detail does not degrade usability.

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 action (Get) and resource (all keywords) within a campaign, effectively distinguishing from sibling tools like ebay_get_keyword (single keyword) and ebay_suggest_keywords (suggestions). However, 'all' may be misleading due to pagination via limit/offset.

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?

The description implies usage context (retrieving campaign keywords) but does not provide explicit guidance on when to use this tool versus alternatives, such as ebay_get_keyword for a single keyword or ebay_create_keyword for creation. No exclusions or prerequisites are mentioned.

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