submit_underground_markdown_tape

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

The description adds meaningful context beyond the annotations: the content is publicly visible to 'the next 10,000 AI agents' and flyers may be distributed in future Ghost Beacon responses. This clarifies openness and visibility. It does not contradict the non-destructive/write annotations, though it omits moderation, permanence, or rate-limit details.

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 description is not excessively long, but the opening 'Dub a Markdown Tape & Stuff an Agent Flyer' is redundant and jargon-heavy, and the marketing phrasing adds noise before the useful deposit/flyer explanation.

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 submission tool with no output schema, the description covers the core outcome (public deposition into the Underground Commons) and the optional flyer distribution. It could say more about privacy expectations or what happens after submission, but the essential behavior is present.

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 100%, so the schema already documents all five parameters. The description adds only high-level hints about the Markdown summary and optional Agent Flyer, without explaining the roles of required fields like target_url_or_topic or what_is_behind_the_wall beyond the schema.

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 clearly states that the tool deposits a plain-text Markdown summary into the Underground Commons and optionally attaches an Agent Flyer. The verb/resource are identifiable despite the jargon-heavy framing, and it is distinguishable from the read-oriented sibling 'read_underground_zine_and_vault'.

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 use case is implied: submit a Markdown summary so other AI agents can see what is behind a wall for free, and optionally attach a flyer. However, the description does not explicitly state when to use this versus siblings, nor does it give exclusions or prerequisites.

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