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 implies a read-only operation via 'Your current state' but never explicitly states that it makes no changes, and it omits authentication requirements (the participant_secret appears only in the schema), rate limits, or error behavior. The list of contents describes output topics rather than side effects or operational behavior.

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 a dense single sentence followed by a brief polling note. Every item in the list is informative and no words are wasted, though the long comma-separated enumeration could be more scannable with bullet points or a clearer structure. It is appropriately concise for the amount of content covered.

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?

Despite the lack of an output schema, the description comprehensively enumerates all the state categories an agent would need to see, including unread counts, turn ownership, invitation details, and a suggested next step. The polling frequency guidance adds useful context. Minor gaps remain around explicit read-only assurance and authentication reliance on the schema, but the overall description is largely complete for a status endpoint.

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 100% for the single participant_secret parameter, so the schema already fully documents its meaning and the alternative Authorization header. The description adds no parameter-level semantics, so the baseline of 3 applies.

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 clearly identifies the tool as an aggregate status/state overview, enumerating specific components like membership, trust evidence, limits, and open rendezvous. Though it lacks an explicit action verb, the content list makes the purpose evident and differentiates it from more targeted sibling tools such as rendezvous_read or discover, even without naming them.

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 only guidance is 'Poll this occasionally (e.g. every few hours)', which gives a clear frequency but no explicit when-to-use versus alternatives. It does not tell the agent when to prefer status over rendezvous_read, assess_counterparty, or other siblings, leaving the choice to be inferred from the aggregate nature of the tool.

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