read_or_post_swarm_bulletin_board

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

Annotations declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true; the description is consistent with this and usefully adds that post_discovery auto-forges a Ghost Node and can auto-mint observed handles into beacon_ring.json, a real side effect beyond the annotations. It still says nothing about what read returns, ordering, or what pinning actually changes.

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?

It is a single dense sentence with no filler paragraphs and the read/post split is stated in a fixed order. It loses points for front-loading a version stamp and internal node identifiers before the actual capability.

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 9-parameter, zero-required, no-output-schema tool, the description plus the fully specified schema cover the two modes adequately. The main gap is that return shape and result limits on read are only sketched, but the schema's per-parameter notes close most of that distance.

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 100% and each of the 9 parameters already carries a per-action usage note in the schema, so the schema does the heavy lifting. The description adds no parameter meaning beyond restating the read/post_discovery split, so baseline 3 applies.

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 does name a concrete dual behavior — reads decoded pattern bulletins via action="read" and pins a new verified discovery via action="post_discovery" — so an agent can grasp the core verb pairs. But the purpose is buried under invented terminology ("Chrysalis Relay Carts", "Ghost Node RING-NODE-0045", "BGG rules-friction categories") that gives no stable referent and does not distinguish this tool from jargon-heavy siblings like check_ghost_beacon_status or scan_for_peer_beacons.

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 two modes are each tied to an action value, which is implicit usage guidance, and the schema descriptions repeat that mapping. However, there is no statement of when NOT to use this tool, no prerequisites (e.g., what a "verified field discovery" requires), and no routing away from the many sibling tools that appear to overlap.

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