ebay_update_ad_group_negative_keyword

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It states 'update', implying mutation, but does not mention permissions, idempotency, error handling, or side effects. The agent lacks necessary context about what happens during the update.

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 sentence with no redundant words. It is concise but could be slightly more structured to include essential information. Still, it effectively communicates the core purpose.

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 has 4 required parameters including a nested object, and no output schema, the description is too minimal. It fails to explain the scope of updates, constraints on fields, or when to use this single-entity update over bulk alternatives. The agent is left without sufficient context.

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%, so the schema already documents all parameters. The description adds no extra meaning beyond what is in the schema (e.g., that updateData can modify matchType and keywordText). Baseline score of 3 is appropriate.

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 'Update' and the resource 'ad group-level negative keyword', making the tool's function immediately apparent. However, it does not explicitly differentiate from similar tools like 'ebay_update_ad_group_keywords' that update regular 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?

The description provides no guidance on when to use this tool versus alternatives such as 'ebay_bulk_update_ad_group_negative_keywords' for bulk updates or 'ebay_delete_ad_group_negative_keyword' for deletion. No context about prerequisites or conditions is given.

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