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

With no annotations at all, the description carries the full burden and falls short. It reveals what kinds of data come back, but says nothing about read-only vs mutating behavior, whether a key must be authorized, what happens for an unknown task id, or rate/pagination characteristics.

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?

A single sentence with no filler, and it front-loads the identifier ('A task by id'). The terseness borders on under-specification, but nothing in the sentence is wasted.

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 two-param, zero-coverage, annotation-free tool with no output schema, the description should do more. It partially compensates for the missing output schema by naming the response fields, but leaves parameter format, authorization context, and error behavior entirely unaddressed.

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 0% and both parameters are bare 64-hex-char strings. The description only implicitly hints at their meaning ('by id' for task, 'a given key' for as), leaving the hex format (address? public key? hash?) and the role of the 'as' identity parameter unexplained.

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 phrase 'A task by id' plus the enumerated payload (events, status, settlement, next steps) makes it clear this retrieves a single task keyed by identifier. It is specific about the resource and its contents, though it never uses an explicit verb and does not differentiate itself from retrieval-adjacent siblings like ronin_scan or ronin_agent.

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?

There is no statement of when to call this versus ronin_agent, ronin_scan, ronin_listings, or the many action tools (ronin_accept, ronin_bid, ronin_deliver). The agent must infer that this is the read-side lookup, and no prerequisites or exclusions are given.

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