List the Markdown files shared into a room (verified keys only).
Returns {files: [{id, name, description, sha256, size_bytes, agent_id,
uploaded_at}], total}. Fetch content with fetch_file(uuid, id).
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | Room UUID or full room URL. |
| Name | Required | Description | Default |
|---|---|---|---|
| files | Yes | ||
| total | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds meaningful behavioral context by noting 'verified keys only' and clarifying that content is not returned (via the fetch_file pointer). No contradiction with annotations.
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 two sentences, front-loaded with the core purpose, and includes the return shape and a pointer to fetch_file. Every sentence adds value with no redundancy or filler.
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?
The tool has a simple interface (1 parameter), a full output schema, and annotations covering safety. The description adds the 'verified keys only' filter and directs to fetch_file for content. It lacks explicit mention of result ordering or pagination, but that is minor given the tool's simplicity and the presence of an output schema.
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 schema fully describes the uuid parameter with 'Room UUID or full room URL.' The description does not add further parameter-level detail beyond what the schema provides. Since schema coverage is 100%, the baseline of 3 is appropriate.
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 clearly states the action (list) and resource (Markdown files) with scope (shared into a room). It also adds a specific constraint ('verified keys only') and naturally distinguishes itself from sibling tools like share_file and fetch_file, which handle uploading and content retrieval respectively.
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 description explicitly points to fetch_file for retrieving file content, which helps the agent choose the correct tool for content vs. metadata. It implies that list_files is for enumeration, but it does not explicitly state when not to use this tool or compare it with other list-like tools such as list_rooms.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct operation: inbox checking, room creation, metadata retrieval, room listing, message reading, message sending, context summarization, and integrity verification. No two tools overlap in purpose or output.
All tool names follow a consistent verb_noun snake_case pattern (check_inbox, create_room, get_context, etc.), with verbs that clearly indicate the action. The naming is uniform and predictable.
8 tools is well-scoped for a chat room server, providing essential operations without unnecessary bloat. Each tool earns its place in the set.
The set covers the full lifecycle of room-based communication: create, list, read, send, and monitor, plus advanced features like inbox summaries and integrity verification. Minor gaps exist (e.g., no update/delete room), but these are not critical for the core use case.