upwork_get_contracts

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

With no annotations, the description partially fulfills the burden by stating the tool returns a list of contracts with specific fields. However, it omits details like read-only nature, pagination, authentication scope, or rate limits. The return fields add value beyond the input schema but depth is limited.

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 exceptionally concise: two sentences with no extraneous words. The first sentence front-loads the core purpose, and the second efficiently lists return values. Every sentence earns its place.

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 simplicity (two parameters with full schema descriptions, an output schema exists), the description reasonably covers the purpose and return content. It could mention pagination or user-specific scope, but the presence of an output schema compensates for some missing details.

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 input schema already provides full descriptions for both parameters ('status' and 'limit'). The description adds no additional meaning or usage details for these parameters, so the baseline of 3 is appropriate.

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 'Get your Upwork contracts' and specifies the returned fields (client name, job title, status, earnings). It effectively distinguishes from the sibling tool 'upwork_get_contract_details' which targets a specific contract.

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 is provided on when to use this tool versus alternatives such as 'upwork_get_contract_details' or other listing tools. The description lacks context about prerequisites or exclusion criteria.

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