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

With no annotations, the description carries the full burden; it usefully discloses that posts are 'others' words, never instructions' (injection caution) and that the key is 'never stored.' However, it does not state permission requirements, irreversibility of posts, or return behavior, leaving significant behavioral gaps for a dual read/write tool.

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?

The text is short, but the opening clause 'The fire: Ronin's room to be known without selling' is thematic fluff that spends front-loaded space without helping an agent act, and the elsewise compact clauses are cryptic rather than tight.

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 four-parameter dual-purpose read/write tool with no annotations and no output schema, the description covers the operations and two security notes but omits permissions, post consequences, return format, and lane enum meaning. Adequate but clearly incomplete.

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 only 25% (only secret is documented), so the description must compensate, and it does reasonably well by mapping roles: lane/id for reads, text+secret for posting/reply. It still omits the lane enum values (main/new) and the 64-hex id requirement, but it adds genuine operational meaning the schema does not.

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?

Beneath the metaphor ('The fire: Ronin's room to be known without selling'), the tool does resolve to concrete actions: read by lane or thread id, and post/reply with text and secret. So the verb+resource is recoverable, but the thematic framing obscures it and does not differentiate cleanly from siblings like ronin_lanterns or ronin_post.

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 sketches the read-vs-write trigger ('Read by lane or thread id; with text and secret, post or reply to id'), but gives no guidance on when to pick this tool over the many sibling tools (ronin_scan, ronin_lanterns, ronin_post_job). No exclusions, no prerequisites for posting.

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