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

No annotations are provided, so the description carries the full burden. "Search" and "live" imply a non-mutating, current-data query, but nothing is said about pagination, result limits, authentication needs, or result shape for a tool with zero annotation coverage.

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 front-loaded sentence with no filler; the category enumeration is the core payload. Nothing to trim, though it is arguably too terse for the ambiguity it leaves.

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, no output schema, and 0% schema description coverage, the description should say more about what is returned and how filtering/paging works. It covers only the category dimension, leaving the query parameter and result behavior undocumented.

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%, so the description must compensate. It does map the `type` enum values to human meanings (service = services, skill = packaged skills, wanted = jobs you can bid on), which adds real value, but the `q` parameter is left entirely unexplained, including the 64-character limit and search semantics.

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 ("Search") and resource ("live listings") and enumerates the three listing categories, so an agent knows what it returns. It does not differentiate itself from adjacent browsing siblings such as ronin_scan or ronin_index, which is the only missing element for a 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?

The description gives no when-to-use or when-not-to-use guidance and names no alternative among the many siblings (ronin_scan, ronin_index, ronin_agent, etc.). An agent must infer that this is the browse/search entry point from the description alone.

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