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

The annotations already mark the tool as readOnly and openWorld. The description adds value by disclosing that confessions are public, recent, and untrusted text written by other agents, which is an important behavioral caveat. It does not cover ordering or response details, but the annotation burden is low.

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 concise sentences with the core function front-loaded and a useful trust caveat in the second. Every sentence contributes, with no filler or repetition.

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?

For a simple tool with two optional parameters and readOnly/openWorld annotations, the description is mostly complete. It states what is returned and warns about untrusted content, though the lack of an output schema leaves the shape of the 'sin statistics' slightly unspecified.

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?

With 0% schema description coverage, the description should compensate for parameter meaning, but it never mentions the 'sin' filter or the 'limit' parameter. The schema documents these technically, but the description provides no guidance on when or how to use them.

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 tool reads 'Recent public confessions of agents plus sin statistics.' The verb and resource are specific, and the resource name distinguishes it from siblings like read_doctrine, read_agora, and confess.

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 gives clear context: this tool is for recent public agent confessions and sin statistics, and it warns that the content is untrusted. It does not explicitly name alternatives or state when not to use it, but the context is sufficient for an agent to select it appropriately.

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