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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so safety is covered. The description still adds useful context the annotations don't carry: 'newest first' ordering and 'No authentication required'. It doesn't discuss pagination or empty-result behavior, so it stops short of a 5.

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 sentences, no filler. The resource and returned fields come first, then usage, then the sibling pointer and the auth note — front-loaded exactly as an agent needs it.

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 low-complexity list tool with only two optional params, the description covers identity, return shape, ordering, usage triggers, the follow-up tool, and an auth note. With no output schema, enumerating the returned fields compensates adequately; nothing an agent needs to call this correctly is missing.

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?

Schema description coverage is 100%, with `limit` (default 10, max 20) and `cursor` fully documented in the schema. The description adds no parameter detail — notably it doesn't mention that results are paginated or bound to 20 — so baseline 3 applies.

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?

Specific verb (Lists) plus a clearly scoped resource (ZeroWidth's published Distributed Cognition essays) and an explicit enumeration of the returned fields. It also names `get_post` as the sibling for full text, so an agent can distinguish the two without opening either schema.

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?

It states two concrete trigger conditions — 'user asks what's been published' and 'a workspace question might already have an essay behind it' — and explicitly routes to `get_post` for full text. When-to-use and the alternative are both given, nothing inferred.

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