yd_bids_set

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

No annotations provided. The description implies a write operation ('Set') but does not disclose effects like overwriting vs. merging, required permissions, or rate limits.

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 single-sentence description is concise and front-loaded, but it is too terse, omitting necessary details that reduce its value.

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 an array parameter with nested objects and no output schema, the description is incomplete. It does not explain return values, error scenarios, or the relationship to other bid-related tools.

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?

The description does not add any parameter-level details beyond the schema. Schema coverage is 50% (client_login described, keyword_id lacking), but the description fails to clarify the 'bids' array structure or the meaning of 'set'.

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 'Set bids for keywords' states the verb and resource, but it is ambiguous among siblings like yd_keyword_bids_set and yd_bid_modifiers_set. The name yd_bids_set could imply any bid type, but the context shows a more specific sibling exists, creating confusion.

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 on when to use this tool vs alternatives (e.g., yd_keyword_bids_set_auto). No when-not-to-use or prerequisites mentioned.

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