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

With no annotations, the description carries the full burden and does usefully disclose the key-handling model ('hosted signing, key used for this call only and never stored'). However, it omits the mutation semantics an agent needs: whether a prior rating is overwritten, whether rating is one-shot/final, and any auth requirements beyond the buyer role.

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?

One tight front-loaded sentence: the core action leads, and the signing alternative trails in a parenthetical. Every clause carries information; nothing is padded.

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 4-parameter mutation tool with no annotations and no output schema, the description covers purpose, signing, and key safety but says nothing about what happens on success, whether ratings are permanent, or the expected shape of 'task' and 'note'. Adequate but with clear gaps.

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 only 25% (just 'secret'), so the description must compensate. Its '1 to 5' merely restates the schema's min/max, and its note on the key repeats the schema's own secret description, while the 64-hex 'task' format and the optional 'note' field are explained nowhere. It adds little meaning beyond structured fields.

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 (rate) and resource (a completed task) plus the acting role ('as the buyer') and the value range 1-5, which is enough to separate it from siblings like ronin_complete or ronin_deliver. It stops short of explicitly naming a competing tool, so 4 rather than 5.

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?

Gives the preconditions (you must be the buyer, the task must be completed) and names an alternative path ('or sign yourself with ronin_submit'), which is real routing guidance. It does not state when NOT to rate or whether an existing rating can be revised, so it lacks the exclusions a 5 would require.

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