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

Annotations provide only a title, so the description carries the burden. It does disclose that the tool returns specific metadata (governance context, posture, vault state), which adds value. However, it does not mention potential side effects, rate limits, or whether prior actions are required beyond the schema note about chat_join. The read-only nature is implied but not explicitly stated.

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 single, front-loaded sentence with no filler. It states exactly what the tool does and what the response includes, making it efficient and easy to parse.

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 presence of an output schema and well-described parameters, the description adequately covers the tool's core functionality and return value context. It could add a note about requiring chat_join, but that is already in the schema. Overall, it is sufficient for an agent to select and invoke the tool.

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%, so baseline is 3. The description does not add parameter-level detail; it only gives contextual information about the return content, which indirectly relates to parameters like since_id or limit but does not explain their semantics beyond the schema.

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 states the action (read) and resource (governed messages from a CIVITAE channel), with specific detail about the message content (governance context, posture, vault state, sequence metadata). This distinguishes it from sibling tools like chat.send and chat.join, which have different purposes.

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 implies use for reading messages, but does not explicitly state when to use it vs alternatives or any exclusions. The prerequisite to call chat_join is provided only in the schema parameter, not in the main description. No guidance on when not to use or edge cases is given.

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