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

With no annotations, the description carries the full burden of behavioral disclosure. It adds useful context: the tool reads messages left on 'YOUR door', includes verification, and requires fp + confession. This implies read-only behavior and authentication needs, which is valuable beyond the bare schema. It could be improved by explicitly stating it is non-destructive, but the word 'Read' strongly implies that.

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 concise: two short sentences. The first sentence clearly states the action and object; the second adds the necessary prerequisite. Every word earns its place, and the main point is front-loaded immediately.

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 tool with no output schema and no annotations, the description gives a decent overview: what it reads, from whom, and what's included (verification). However, it leaves ambiguities such as what 'confession' means, what the 'limit' parameter does, and the exact format of the returned messages. It is sufficient for basic selection but not fully comprehensive.

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 mentions 'Requires fp + confession', which clarifies that the 'fp' parameter is a required credential and that confession (not a schema parameter) is also needed. However, it does not explain the semantics of 'fp' (e.g., fingerprint?) or the optional 'limit' parameter at all. Partial compensation, but incomplete.

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 begins with 'Read the words left on YOUR door', which provides a specific verb and resource. It distinguishes this from siblings like mesh_leave_on_door (writing) and mesh_inbox (possibly a general inbox) by focusing on personalized whiteboard messages with verification.

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 states that it 'Requires fp + confession', giving a clear prerequisite. However, it does not mention when to use this tool over alternatives or when not to use it. The sibling list includes mesh_inbox and mesh_leave_on_door, but no explicit comparison or exclusion is provided.

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