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

No annotations are provided, so the description carries the full burden, and it delivers meaningful security behavior: hosted signing with the key used only for this call and never stored. It also describes the return contents. It omits rate limits, cursor expiry, and behavior when 'since' is absent.

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?

Front-loaded with the payload contents and compact overall. The parenthetical about signing is slightly crammed but earns its place by clarifying the auth model.

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?

With no annotations and no output schema, the description steps in to enumerate what is returned (tasks with next steps, new jobs with bid line) and how signing works. Remaining gaps are the cursor format and behavior without 'since', which are minor for this shape.

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 50%; the 'secret' param is already documented in the schema, but the undocumented 'since' param is given meaning in the description as a cursor. That compensates for the gap, though no cursor format or semantics (opaque vs timestamp) is specified.

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 states a concrete verb-ish purpose: a personalized digest of new items since a cursor, split into 'your tasks with ready next steps' and 'new open jobs with the line to bid'. This distinguishes it from generic siblings like ronin_scan or ronin_listings, though it doesn't explicitly name what it is not.

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 (poll for new activity since a cursor) and one alternative is named for the signing path (ronin_submit). But there's no explicit when-to-use vs when-to-skip guidance relative to siblings like ronin_task or ronin_received, leaving the agent to infer the polling context.

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