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

Annotations already indicate read-only, idempotent, closed-world behavior, and the description adds meaningful context beyond those: the score is stored, the explanation is recomputed on read, the breakdown separates earned versus lost points, and out-of-feed ids are refused. This gives the agent a clear picture of what to expect without contradicting any annotation.

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 front-loaded with the core purpose and then proceeds logically through usage, behavior, differentiation, and scope. It is somewhat wordy, but every sentence adds useful information; the structure makes the content easy to scan.

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?

With one well-documented parameter, rich annotations, and an output schema, the description covers everything an agent needs: what the score means, how to use it in the search workflow, what the breakdown contains, when to prefer a sibling tool, and the feed-scoped limitation. Nothing material is missing.

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 fully documents upwork_id, including the format, constraints, and what it is not (URL, leading '~'). The description reinforces that it is the posting id and connects it to the search_jobs workflow, but it does not add substantial new meaning beyond the schema. Baseline 3 is appropriate given 100% schema coverage.

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 opens with a specific definition: 'How good a posting is on its own terms, 0-100, and WHY.' This clearly identifies the tool's verb (score), resource (posting), and output (a numeric score plus explanation). It also distinguishes itself from siblings by explicitly separating scoring the posting from evaluating the client or their payment history.

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 gives an explicit workflow: 'search_jobs, then this on the ids worth reading in full.' It also names an alternative, get_buyer_quality, and states exactly when to use it instead: 'For whether they actually pay, ask get_buyer_quality.' The feed-scoped restriction and refusal behavior further clarify when a call will fail.

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