upwork_get_conversation

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

No annotations are present, so the description bears full burden. It claims to return 'full message history' but the input schema includes a 'limit' parameter with a maximum of 100, implying the history may be truncated. This contradiction is not addressed, and no information about authentication, rate limits, or side effects is provided.

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 with no redundant information. However, the first sentence could be more precise to avoid the 'full history' contradiction with the limit parameter, which slightly detracts from clarity.

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 no output schema, the description vaguely mentions returning 'conversation details with full message history', but does not specify the structure or fields of the response. Given the simplicity of the tool (listing messages), this is minimally adequate but lacks detail for complex agent reasoning.

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?

Although schema coverage is 100% (both parameters have descriptions), the tool description adds little value beyond the schema. The phrase 'full message history' conflicts with the limit parameter, potentially misleading the agent. The description does not explain parameter relationships or provide context not already in the schema.

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 verb 'Get' and the resource 'messages in a specific conversation', making the purpose unambiguous. It implicitly distinguishes from the sibling tool 'upwork_get_messages' by specifying 'in a specific conversation', but does not explicitly contrast them, so it falls short of a perfect score.

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 the sibling 'upwork_get_messages', nor are any prerequisites or exclusions mentioned. The description simply states what it does without contextual usage advice.

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