Place a Bid

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

The description warns that this creates a real bid, advising review before confirming, and clarifies the role of the account parameter. This adds significant behavioral context beyond the annotations, which only show non-read-only and non-destructive hints.

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 well-structured with an Args block, warning, and usage examples. While relatively long, each section serves a purpose and adds value, making it efficiently informative.

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 with 6 parameters and no output schema, the description covers all parameters, specifies return values (confirmation with bid ID and status), and includes a critical warning about real-world consequences.

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%, but the description adds meaningful context, such as 'milestone_percentage default 100' and that account specifies which account the bid is placed FROM. This clarifies usage beyond the schema's base descriptions.

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 'Submit a bid / proposal on a Freelancer.com project,' using a specific verb and resource. It distinguishes itself from sibling tools like freelancer_get_project_bids (which only reads bids) by emphasizing the act of placing a bid.

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 includes example queries like 'Bid $150 on project 12345 with 7 days delivery,' indicating when to use it. It also refers to freelancer_list_accounts for account selection but does not explicitly exclude scenarios where other tools should be used.

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