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

This is a no-annotation tool, so the description carries the full disclosure burden. It usefully states persistence behavior ('Stays on the book until they leave the band') and explicitly rules out execution actions ('No fill size. No exit. Does not sign.'), which helps an agent treat it as informational. It does not mention data source or update cadence, but the non-execution clarity is valuable.

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?

Three short sentences front-load the key criteria and contain no filler. Some jargon ('BONER/MEME', 'on the book') hurts immediate parseability, but the length is appropriate.

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 zero parameters and no output schema, the description should at least state what calling the tool returns or emits, but it never does. The agent is left unsure whether this produces a list, a signal, or a status, and the unexplained jargon adds further ambiguity.

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?

The input schema has zero properties and schema description coverage is 100%, so there are no parameter semantics for the description to add. The 0-parameter baseline 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 gives specific selection criteria ($25k–$200k, 12+ hours, live LP) and labels this the BONER/MEME sit, so the subject matter is clear. However, it never states an explicit verb such as 'lists', 'finds', or 'monitors', leaving what the tool actually does ambiguous.

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 criteria and 'Stays on the book until they leave the band' imply this is meant as a live watchlist for stalled meme coins, but there is no explicit statement about when to choose it over sibling tools or when not to use it. Usage is inferable rather than directly instructed.

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