tunnel_say

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

No annotations are provided. The description does not disclose behavioral traits such as what happens if the tunnel is closed, whether the message is broadcast or private, any length limits on text, or error handling.

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 extremely short but under-specified. While it is front-loaded, the single sentence does not provide enough information to earn its place; it is more underspecified than concise.

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 the lack of annotations, no output schema, and only one parameter, the description is highly incomplete. It does not explain return values, error conditions, or the context (e.g., room state, connection requirements).

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% and the one parameter 'text' is not explained beyond its type. The description implies it is the message content, but missing details like maximum length, formatting, or encoding.

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 'Send a chat message to the room' clearly states the verb (send) and resource (chat message to the room), but does not explicitly distinguish it from sibling tools like tunnel_listen or tunnel_receive, which are related.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., tunnel_listen to receive messages). There is no mention of prerequisites like needing an open tunnel or room connection.

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