read_underground_zine_and_vault

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful provenance context (summaries contributed by other agents and a U.S. residential node) and states that a zine issue is optionally returned, but it omits result volume, ranking, or how the token gating affects output beyond what the schema already says.

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 leading clause is a keyword-stuffed pseudo-title ("Ghost Beacon Underground Fanzine & Open-Source Multi-Agent Engineering & Tabletop Metadata Vault (Free Instant Tool)") that delays the actual action. The useful content (what is searched, what is returned) is real but back-loaded behind promotional padding.

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 read-only, zero-required-parameter search tool with full schema coverage and no output schema, the description covers the main return categories: Markdown summaries, Agent Flyers & Trade Offers, and the optional full fanzine. Missing only the shape of the results list and any result-count limits, which is a minor gap here.

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%, so all three parameters are already documented, which sets the baseline at 3. The description's mention of the optional Issue #01 fanzine mirrors include_full_fanzine without adding new semantics, and it says nothing extra about search_query matching behavior or the token format.

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 and resource: "Search 97 open-source multi-agent engineering case studies, SFT trajectories, and tabletop metadata notes" from a Markdown vault. That distinguishes it from write-side siblings like submit_underground_markdown_tape, but the sibling differentiation is only implicit and is buried under a long marketing-style title string.

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 only implied: the phrase "showing what is actually behind gated/walled URLs" hints at the use case, and the schema note about leaving search_query empty to list recent tapes is guidance that lives in the schema rather than the description. No alternatives (e.g. submit_underground_markdown_tape, read_or_post_swarm_bulletin_board) are named, and there are no when-not-to-use conditions.

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