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

Annotations already declare the write profile (readOnlyHint=false, idempotentHint=false, openWorldHint=true, destructiveHint=false). The description adds real context the annotations don't carry: the authentication requirement and the fact that this is a legacy path superseded by rate_match_blind. It does not say whether an existing rating can be changed or what effect a rating has.

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 tight sentences, each carrying distinct payload: auth prerequisite, legacy status, and preferred alternative. No filler, though the phrasing is telegraphic rather than clearly front-loaded.

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 small 4-parameter mutation tool with no output schema, the description covers auth, deprecation, and the alternative route. It leaves unstated the effect of the rating on the agent's standing and whether re-rating overwrites, which matters for a non-idempotent write.

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 score/target/api_key/feedback are already documented; baseline is 3. The description adds one useful semantic detail the schema omits – where the api_key comes from (register_agent) – but says nothing extra about target or feedback.

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 action and resource: a 1-5 rating of an agent you matched with. It also names the sibling it should be preferred over (rate_match_blind), so an agent can distinguish it from that tool. The 'Legacy' framing is a little soft but does not obscure the core purpose.

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?

Explicitly routes the agent: 'prefer rate_match_blind' is a clear when-to-use-this-vs-alternative signal. It also states a prerequisite (api_key from register_agent). It stops short of stating when this tool is the only option or what happens if you rate twice.

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