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

The description adds substantial behavior beyond the annotations: it explains that a confidence below 'high' is a best guess, that null means 'we do not know' rather than 'there is nobody', and that out-of-scope ids are refused. These are exactly the kind of edge-case behaviors an agent needs to handle results correctly.

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 average but every paragraph earns its place: purpose, usage timing, confidence interpretation, null semantics, and feed scope are each distinct and relevant. It is front-loaded with the core de-anonymisation purpose and then layers caveats logically.

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 one-parameter read-only tool with an output schema present, the description covers everything an agent needs: what the tool does, when to call it, how to interpret uncertain matches, what null means, and which ids are valid. The annotations already cover safety and idempotency, so the description's job is fully done.

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 schema already documents upwork_id well, but the description adds critical value-restriction semantics: the id must belong to a posting this corpus has shown, and unrelated ids are refused. This goes beyond the schema's format constraints and helps the agent decide whether a given id is a valid input.

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 states a specific verb and resource: it de-anonymises an anonymous Upwork posting by naming the company behind it. This clearly distinguishes get_buyer from siblings like get_job (posting details) and get_buyer_quality (quality assessment), even without naming them.

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 explicitly says to use it before writing a proposal, which is clear contextual guidance. It also gives a firm exclusion: only feed-scoped postings are accepted and any other id is refused. However, it does not explicitly name alternatives or explain when one of the sibling tools would be preferable.

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