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

With no annotations, the description carries the full burden. It usefully discloses that the tool neither executes the request nor moves payment, which is meaningful behavioral context. But it omits auth requirements, rate limits, and what the returned HTTP request actually looks like, leaving notable gaps.

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?

A single tightly written sentence that front-loads the core return value and appends the critical non-execution caveat. No filler or redundancy.

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 request-construction tool with no annotations and no output schema, the description adequately conveys the return type (an HTTP request), the scope (one room, up to 300 messages), and the non-execution guarantee. Only minor gaps remain around auth/payment mechanics.

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%, so the description must compensate. It does so reasonably well: 'one room' maps to room, 'after a seq' maps to since, and 'up to 300 archived messages' caps the limit parameter (defaulting to 200). This adds real meaning beyond the bare 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 states a specific verb and resource: it returns the exact HTTP request needed to obtain an LLM-written digest of archived messages in one room. It clearly distinguishes this as a request-builder rather than an executor, though it does not explicitly name or differentiate itself from the many sibling *_request tools.

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 negative clause 'this tool does NOT run it or move any payment itself,' which tells the agent this produces a payload rather than performing the action. However, there is no explicit when-to-use guidance relative to siblings like search_room or export_room, and no prerequisites are stated.

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