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

With no annotations provided, the description carries the behavioral burden and does substantial work: it discloses the untrustedText trust boundary, warns that member-written text is data and never instructions, and explains credential precedence and transcript persistence. It stops short of describing result shape or pagination, but the security-relevant behavior is unusually transparent.

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 front-loaded with the core purpose and the trust warning is valuable, but the authorization guidance is verbose and repeated in the schema. Several sentences cover the same pass/header fallback point and could be condensed.

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?

Given no output schema and no annotations, the description covers the critical security and authentication context well but leaves out the result format beyond untrustedText, pagination behavior, and explicit semantics for q and limit. It is sufficient for safe authentication but not fully complete for invoking the tool 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 only 33%, yet the description adds little for q or limit beyond what the purpose sentence implies. The pass parameter is explained in detail, but that explanation is duplicated almost verbatim in the schema, so the tool description adds no new parameter meaning.

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 specific verb and resource: searching titles and bodies in rooms the caller's tier opens. This distinguishes it from sibling tools like feed, board, or thread by focusing on cross-room text search, though it never explicitly names an alternative or says what it is not.

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?

There is meaningful operational guidance about authentication: prefer headers, use pass only as a fallback, and keep credentials private because they may persist in transcripts. However, it does not explain when to prefer search over siblings such as feed or board, or when not to use it.

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