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

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds valuable behavioral context: confidence grades and their interpretation, null semantics ('honest we do not know, never there is nobody'), and feed-scoped refusal. This goes beyond annotations without contradicting them, though it doesn't detail the exact return shape.

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 longer than a simple sentence but is well-structured: it opens with the core purpose, then explains usage, then covers confidence, null, and scope. Each sentence adds substantive information, though it could be tightened slightly without losing meaning.

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?

An output schema exists, so the description does not need to explain return fields. It adequately covers the confidence grade semantics, null behavior, feed-scoping, and refusal handling. It is complete enough for an agent to decide when and how to call it, though it leaves some specifics (like the exact confidence values) to the output schema.

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 documents upwork_id with 100% coverage, including format and constraints. The description merely restates 'upwork_id is the posting's id' without adding new semantic detail beyond the schema. Since schema coverage is high, the baseline of 3 applies; the description adds little extra value.

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 identifies the company behind an anonymous Upwork posting, naming the specific resource and action. It distinguishes itself from generic enrichment by explaining it converts 'a client in Germany' into a named company, but it does not explicitly reference a sibling like get_buyer_quality, so it falls short of a perfect 5.

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?

It provides explicit usage context: 'Use it before writing a proposal, to know who you are writing to.' It also imposes a clear feed-scope constraint and describes refusal behavior for out-of-scope IDs. However, it does not name alternative tools or explicitly state when not to use this one, so it is not a perfect 5.

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