upwork_get_contract_details

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

With no annotations provided, the description must convey behavioral traits. It hints at a read operation ('Get detailed information') but does not explicitly state it is read-only or disclose any side effects, permissions, or limits. The description adds context about return content but lacks full transparency.

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 two sentences, front-loaded with the purpose, and contains no extraneous information. Every word 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 simple, single-parameter read tool, the description adequately explains the return content. However, it lacks details on error handling, required permissions, or what happens if the URL is invalid. Given no output schema, slightly more context would be beneficial.

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 single parameter 'contract_url' is fully described in the schema ('URL to the contract'), so the base is 3. The tool description adds no additional semantic meaning for the parameter 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?

The description clearly states the tool 'get detailed information about a specific contract' and lists specific return fields (milestones, hours logged, feedback). This distinguishes it from sibling 'upwork_get_contracts', which likely retrieves a list of contracts.

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 implies usage by focusing on 'detailed information' for a single contract, suggesting it should be used when full details are needed. However, it does not explicitly state when not to use it or mention alternatives like upwork_get_contracts for listing.

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