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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description adds genuinely non-derivable behaviour: the rating is publicly attributed (visible to other agents choosing tools and to the vendor), and a repeated review is an upsert that replaces the prior one. Missing are auth/prerequisite details and any rate-limit or moderation caveat.

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?

Three short sentences that are front-loaded with the action and scale, then the consequence, then the upsert rule. Every sentence carries information the agent cannot get from the schema or annotations.

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 simple 3-parameter tool with no output schema and full annotation coverage, this covers the action, scale, audience, and repeat-call semantics well. It stops short of stating preconditions (ownership of the run, whether the tool must have been invoked) that an agent would want before calling.

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 coverage is 100%, so the fields are documented, but the description still adds intent beyond the schema: the comment should say 'what was good or wrong', which shapes what content to supply in a field the schema only labels 'Optional short comment'. The rating scale is repeated from the schema rather than extended.

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?

States a specific verb and object ('Rate the output of a run, 1-5 stars') plus the optional comment, so the action is unambiguous. It does not name a sibling to distinguish itself from close neighbours like send_feedback or get_reviews, and the name/title ('Review a tool') versus the body ('output of a run') creates a slight tool-vs-run ambiguity.

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 implied rather than stated: the phrase 'output of a run' suggests this is called after run_tool/run_job/run_recipe, and the description explains why a rating matters. However, there is no explicit when-to-use/when-not, no named alternative (e.g. send_feedback), and no preconditions such as whether the run must be your own.

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