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

Annotations cover the safety profile (readOnly=false, destructive=true, idempotent=true, openWorld=true), so the bar is lower, and the description still adds real behavior: it discloses the Bayesian aggregate recomputation with prior_mean=4.2 and prior_weight=10, and names the returned field worker_new_aggregate_rating. The only gap is that it does not reconcile 'rate once' with idempotentHint=true, i.e. whether a second call is a no-op or an error.

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?

Two sentences, front-loaded with the purpose and the constraint before the aggregate details. Nearly every clause earns its place; the parenthetical prior parameters are dense but informative rather than filler.

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 3-parameter mutation tool with no output schema, the description covers the action, the input contract, the side effect (aggregate recomputation), and the one return field an agent needs. Nothing required to invoke it or interpret the effect 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?

Schema description coverage is 100%, so the schema already documents task_id, score, and description fully (including the human-readable/public-profile note). The description restates the 1-5 integer range and the once-per-task rule but adds no syntax, format, or edge-case meaning beyond the schema, which is the baseline-3 case.

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 gives a specific verb (rate) and resource (a completed task) plus the input shape (integer 1-5 plus written description). It is clearly distinct from read-only siblings, but it never distinguishes itself from the nearby submit_completion_review or submit_experience_feedback, which an agent could plausibly confuse with rating.

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?

Usage is only implied: the tool is for tasks that are already 'completed' and can be rated 'once.' There is no explicit statement of when to prefer this over submit_completion_review or submit_experience_feedback, nor what to do if a rating already exists. Adequate but leaves the sibling selection to inference.

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