ebay_get_negative_keyword

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

Annotations already declare readOnlyHint=true, and the description simply repeats the read intent via 'Get' without adding any behavioral context (e.g., authentication needs, rate limits, return format). No additional insight is provided 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?

The description is one short, complete sentence with no filler. It states the purpose directly and earns its place without wasteful wording.

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 simple tool, the description is adequate for a basic get-by-id operation, but it lacks important context: no mention of return value, no distinction from the plural sibling, and no indication of prerequisites. The single parameter name mitigates ambiguity but does not fully compensate.

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 coverage is 100% for the single parameter, so the baseline is 3. The description adds no information about negativeKeywordId, relying entirely on the schema's minimal 'negativeKeywordId required endpoint parameter' text. No extra meaning is contributed.

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 (negative keyword) and mentions the eBay Marketing API. It is distinguishable from create/update/delete siblings, though it does not explicitly differentiate from the plural ebay_get_negative_keywords.

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 given about when to use this tool versus alternatives like ebay_get_negative_keywords (list) or ebay_create_negative_keyword. The description does not mention that this fetches a single negative keyword by ID or the relationship to the plural variant.

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