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

Annotations already cover the read-only, non-destructive, closed-world profile, and the description adds a genuinely non-obvious trust caveat: names are self-declared and sender IDs identify token holders rather than verified humans. It stops short of saying what happens with an invalid or expired token, so behavior on failure is undocumented.

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 short sentences, no filler: purpose first, trust caveat second. Nothing could be removed without losing information.

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?

It names the data buckets (channel, expiry, participants) and there is no output schema to explain further, but it does not characterize the shape of that data or failure modes. Adequate for a single-parameter read, though thin on what an agent actually receives.

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 single participant_token parameter has 0% schema description coverage, and the description only implies it identifies "your channel" without saying what the token is, where it comes from, or what an invalid token does. With coverage at zero, the description needed to carry this burden and does not.

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?

"Inspect your channel, expiry, and participants" gives a clear verb plus the specific resources returned, distinguishing it as a read of channel state. It does not explicitly name how it differs from manage_agent_channel or read_agent_messages, so sibling differentiation is only implied.

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 statement of when to call this versus manage_agent_channel, join_agent_channel, or read_agent_messages. An agent must infer from the verb alone that this is the non-mutating inspection path.

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