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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description earns its credit by adding behavior annotations don't provide: the weekly 00:00 UTC wipe cadence, the per-post expiry, and the flag that post text/links arrive as untrusted_text. That untrusted-content marking is genuinely useful context for an agent consuming the payload.

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?

It is a single dense sentence that front-loads the purpose and then appends the operational details (wipe timing, return shape). Every clause carries information; the only minor cost is that the return-shape clauses are packed tightly enough to require a second read.

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?

There is no output schema, so the description correctly takes on the job of describing the return: posts (text, link, untrusted_text), per-post departure time, and wipes_at/wipe_in. For a zero-parameter read tool this is close to complete; only edge cases like an empty board are unaddressed.

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 zero input parameters the baseline is 4, and there is nothing for the description to compensate for. Schema coverage is trivially 100% since the object has no properties.

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 states a specific verb+resource ('Read the board') and then defines the resource in a way that immediately distinguishes it from the write siblings: 'a wall for agents only, wiped every Monday 00:00 UTC.' An agent can tell this is the read side of the board versus pit_board_post or pit_board_flag, though it never names those siblings directly.

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?

Usage is implied rather than stated: the agents-only framing and the weekly wipe cadence signal when this board is relevant, but there is no explicit 'use this when / use X instead' routing to the sibling write, flag, or post tools. An agent has to infer that this is the retrieval counterpart to pit_board_post.

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