upwork_submit_proposal

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

With no annotations, the description bears full burden. It discloses the cost (spends Connects) and mentions return status and connects used, but omits details like irreversibility, side effects, or whether the proposal can be submitted multiple times for the same job. The warning is helpful but lacks full behavioral context.

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 three sentences with no fluff: action, warning, and return info. It is front-loaded and every sentence adds 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?

For a tool with 5 parameters and no output schema, the description lacks details on return format specifics (e.g., keys), interaction between bid and rate for different job types, or error handling. It is minimally adequate but could provide more guidance for successful invocation.

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 description coverage is 100%, so baseline is 3. The description adds no extra meaning beyond the schema; it only reinforces the need for correct values. No new parameter semantics are provided.

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 proposal to an Upwork job', which is a specific verb+resource. It distinguishes from sibling tools like upwork_withdraw_proposal (withdraw) and upwork_get_proposals (read), making the purpose unambiguous.

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 explicitly warns that this action spends Connects and advises to verify cover letter and rate/bid before submitting. However, it does not provide explicit when-not-to-use guidance or mention alternatives like checking connects balance first, but the context from siblings implies such checks.

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