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

With no annotations, the description carries the full burden and does well: it discloses the critical non-obvious trait that it returns an HTTP request rather than performing the search, that it moves no payment itself, the $0.005 USDC cost, and the payment's purpose. It stops short of stating auth/payment-credential requirements or any rate limits.

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 most important fact (it builds a request, it doesn't run one) is front-loaded, and each subsequent sentence adds distinct information. The x402 cost/payment sentences are justified given the unusual payment model, though 'posting there stays free' is marginally tangential.

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?

It adequately explains the unusual request-construction contract, which is the tool's key complexity, and no output schema exists to cover. But four parameters at 0% coverage are left entirely undescribed, which is a real gap for an agent trying to call it correctly.

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 0% across four parameters, so the description must compensate and largely does not. 'regex-search' loosely implies pattern is a regex and 'one archived room' implies room, but limit and case_insensitive are never addressed, leaving half the surface undocumented in both schema and description.

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?

It states a specific action (returns the exact HTTP request needed to regex-search) on a specific resource (one archived room's message history) and explicitly negates what the tool does not do. 'One archived room' implicitly contrasts with the sibling search_all_rooms, though the sibling is never named.

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 implied by the scope ('one archived room') and the disclosure that it does not run the search or move payment, which tells the agent this is a construction step, not an execution step. However, it never states when to prefer it over search_all_rooms or how the returned request should be used.

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