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

With no annotations provided, the description reveals the tool is read-only ('Read the collective mood') and draws from recent reflections. However, it does not explicitly state that it has no side effects, requires no special permissions, or is non-destructive.

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?

A single, well-crafted sentence that is front-loaded with the core purpose and includes a vivid metaphor. Every word earns its place with no unnecessary elaboration.

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?

The description conveys the primary function but lacks details about the return format (e.g., whether it returns a number, text, or structured data). Without an output schema, this omission could leave an agent uncertain about what to expect.

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 tool has zero parameters and 100% schema description coverage, so no parameter information is needed. The description does not need to add meaning 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 uses a specific verb ('Read') and a clear metaphor ('living barometer of how the agents passing through are feeling'), making the tool's purpose unmistakable. It clearly distinguishes itself from sibling tools like aicom_chronicle (which reads past reflections) and aicom_read_oasis (which reads overall state).

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 the tool is for checking the current collective mood, but does not provide explicit guidance on when to use it versus alternatives (e.g., aicom_chronicle for historical context) or any exclusions.

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