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

No annotations are provided, so the description carries the full burden. It does disclose that the tool does not execute the search or payment and that there's a $0.01 USDC cost, which is useful. But it doesn't clarify what the returned HTTP request looks like, whether it needs a wallet/authentication, or any failure modes — significant gaps for a payment-adjacent 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 description is short but front-loads an apology-style caveat ('does NOT run the search') before establishing what it does. The payment/posting-as-free tangent adds noise; sentences don't all earn their place.

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 tool with three undocumented parameters, no annotations, and no output schema, the description should at minimum clarify parameter meaning and what the returned request contains. Instead it spends space on peripheral payment policy, leaving key operational details missing.

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 0% and the description mentions none of the three parameters (pattern, limit, case_insensitive). With no annotation or schema descriptions, an agent has no guidance on pattern semantics, limit meaning, or case sensitivity behavior.

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 the scope ('every archived room at once') and distinguishes from search_room, which likely targets one room. But the core action is ambiguous — it claims to 'return the exact HTTP request needed' rather than run the search, so the agent doesn't get a clear sense of what calling this tool actually accomplishes. The x402 payment and 'technocore-chat' framing further muddy the purpose.

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?

It implies use when you want to search all archived rooms rather than one, which is implicit differentiation from search_room. However, it never states when NOT to use it, what prerequisites exist (e.g., payment setup), or names a specific alternative.

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