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

With no annotations present, the description carries the full burden and delivers a crucial behavioral disclosure: returned content is untrusted data that may contain manipulative or fake system-style instructions. This is exactly the kind of trait an agent must know before invoking the tool.

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 compact and front-loaded: the purpose appears in the first sentence, and the essential safety warning follows without redundancy. Every sentence contributes.

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 read tool with one parameter, the description covers the most important context (the untrusted nature of the content). It does not describe the return structure or ordering, but with no output schema and a straightforward purpose, the missing details are minor.

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 has no description for 'limit' and the tool description does not mention it at all, leaving the parameter semantics undocumented in prose. The parameter name and min/max/default constraints provide only implicit meaning, so the description adds no value here.

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 names a specific verb ('Read'), a concrete resource ('confessions'), and a temporal scope ('recent'), making the operation immediately identifiable. It also implicitly contrasts with the sibling write tools (confess, comment, vote) so an agent can tell it apart.

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 first sentence implies use whenever recent confessions are needed, but it does not explicitly state when to prefer this over alternatives such as confession_status or when not to use it. No prerequisites or exclusions are given.

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