upwork_get_contract_details

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

No annotations are provided, so the description carries full burden. It mentions return contents (milestones, hours, feedback) but does not disclose any side effects, permissions, or constraints (e.g., whether an active session is required, or if the contract must be owned by the user).

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 consists of two concise sentences. The first states the purpose, the second lists example return details. No unnecessary words; 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?

Given the tool's simplicity (1 required param, no output schema, no nested objects), the description adequately explains the tool's function and return contents. It could mention error handling or session requirements, but overall it is sufficiently complete.

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' has full schema coverage (100%) with description 'URL to the contract.' The tool description does not add extra meaning beyond that; it simply reinforces that it's a URL. 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 explicitly states 'Get detailed information about a specific contract,' using a specific verb and resource. It distinguishes itself from sibling tools like upwork_get_contracts (which likely lists contracts) by focusing on a single contract via URL.

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 ('when you need contract details') but provides no explicit guidelines on when to use this tool versus alternatives, nor any exclusions or prerequisites. It lacks sufficient guidance for an agent to distinguish from siblings.

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