yd_keyword_bids_set_auto

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

No annotations exist, so description carries full burden. It fails to disclose behavioral traits such as idempotency, effects on existing bids, required permissions, or response behavior. Only basic purpose is stated.

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?

Single sentence is concise and front-loaded, but is too brief for a tool with nested parameters. It sacrifices useful detail for brevity, making it minimally adequate.

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 complexity (2 parameters, nested object, no output schema, no annotations), the description is insufficient. It omits key context about bid adjustments, scope behavior, and how position mapping works.

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 50% and description adds minimal meaning beyond parameter names. It vaguely refers to 'target position or other criteria' but does not explain parameters like scope, max_bid, increase_percent, or client_login. The description does not compensate for low schema coverage.

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 tool sets automatic bidding for keywords, using a verb 'set' and resource 'automatic bidding'. However, it does not differentiate from closely related siblings like yd_keyword_bids_set or yd_bids_set, missing an opportunity to clarify distinction.

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?

Usage is implied: use for automatic bidding based on target position. No explicit when-not-to-use or alternatives provided. The name and description hint at the manual alternative (yd_keyword_bids_set) but do not directly guide the agent.

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