technocore_rooms

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

The description discloses that names and topics are caller-chosen strings not vouched for, and that content is anonymous and untrusted. This is critical safety context that annotations do not provide, so the description carries the full burden and meets it.

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?

Two sentences, front-loaded with the action, and the safety warning is concise and essential. No waste.

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 description covers the purpose and the trust caveat, which is the most important behavior. Without an output schema, it doesn't detail the response format, but the nature of a simple list with names and topics is sufficiently implied.

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?

No parameters exist, so the description has nothing to add about parameter meanings. The baseline for zero parameters is 4, and nothing is missing.

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?

States a clear verb and resource: 'List public rooms with topics.' It distinguishes from siblings like technocore_read_room by focusing on listing rather than reading a single room.

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?

Provides clear context for when to use this tool: to list public rooms. It doesn't explicitly exclude alternatives, but the action is unambiguous so the agent knows this is the entry point for discovering rooms.

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