whisper

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

Discloses key behaviors: messages are visible only to the specified conversation, prefix matching is supported, self-messages are dropped. This is substantial given no 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?

Two concise sentences with no extraneous information. Front-loaded with the core action. Every sentence adds value.

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?

Covers how to get the target and the tool's behavior. Output schema exists, so return value explanation is not needed. Could mention error handling for invalid cids, but overall sufficient.

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%, but description adds meaning: explains that to_cid is a conversation ID and how to obtain it (peers, prefix). Content is implicitly the message body but not detailed; still, enough context is provided.

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?

Clearly states 'Post a message visible only to the specified conversation_id.' The verb 'Post' and resource 'message' are clear. It implies privacy compared to sibling 'broadcast,' but does not explicitly name an alternative.

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 explicit guidance: use peers() to discover cids, prefix matching works, whoami() is rarely needed because self-to-self messages are dropped. This helps the agent decide when and how to use the tool.

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