Update Bid Form

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

Annotations already provide readWrite nature (readOnlyHint=false, destructiveHint=false). Description adds that it returns the modified object and only supplied fields are changed, which is useful but not extensive beyond annotations.

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?

Concise with two sentences plus API info. First sentence states purpose, second explains behavior. Could be slightly tighter by removing endpoint details, but overall efficient.

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?

Explains partial update and return object, but lacks guidance on optional parameters like base_bid and alternates. For a tool with 11 parameters and no output schema, more detail on complex params would improve completeness.

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 parameters are well-documented in the schema. Description redundantly lists required parameters but adds no new meaning beyond what the schema already provides.

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?

Clearly states 'Update single Bid Form' and explains it updates existing Bid Management records. Distinguishes from sibling tools like 'update_a_bid_from_a_bid_package' by focusing on the bid form itself.

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?

Tells users to use this for updating existing bid forms and mentions partial updates, but does not specify when not to use it or provide alternatives among sibling tools.

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