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

With no meaningful annotations beyond a title, the description carries the burden of behavioral disclosure. It discloses that messages are logged with a SHA-256 provenance seed and are subject to constitutional governance, adding valuable context about side effects and constraints. However, it does not describe failure modes, moderation outcomes, or rate limits.

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 unnecessary words. It efficiently conveys the core action and two key behavioral characteristics (logging and governance), earning its place without redundancy.

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 tool's low complexity, a complete input schema, and the presence of an output schema, the description provides sufficient context. It explains the governed nature and provenance logging, which is adequate for an agent to select and invoke the tool, though it relies on the schema for the join prerequisite.

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 schema description coverage is 100%, so parameters are already fully documented in structured form. The description itself does not add parameter semantics, matching the baseline score of 3.

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 uses the specific verb 'Post' with the resource 'message into a governed CIVITAE channel', clearly distinguishing it from sibling tools like chat.join, chat.read, and chat.status. It also adds context about governance and provenance, making the tool's function unambiguous.

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 the core action ('Post a message') but does not explicitly mention when to use this tool versus alternatives or any exclusions. The required sender prerequisite is relegated to the input schema rather than the description, so usage guidance is implied rather than explicit.

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