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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds non-obvious context beyond that: results are newest-first, no authentication is required, and the exact field set returned. It does not state total counts or truncation behavior, so it falls 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?

Three sentences, zero padding: the resource and ordering come first, then the usage triggers, then the routing hint and auth note. Every sentence earns its place.

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, but the description enumerates the returned fields (title, slug, excerpt, byline, public URL), and pagination is handled by the documented cursor parameter. For a two-parameter read-only list tool, an agent has everything needed to call it and interpret the result.

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% (limit default/max, cursor usage are all documented inline), so the schema already carries parameter meaning. The description adds nothing about limit or cursor semantics, making the baseline 3 appropriate 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?

States a specific verb (Lists) and resource (ZeroWidth's published Distributed Cognition essays), and names the exact return fields plus ordering. It is clearly distinguishable from siblings such as get_post (single essay) and list_docs/search_docs (different corpus).

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?

Gives two explicit triggering conditions ('when the user asks what's been published', 'when a workspace question might already have an essay behind it') and routes the agent to the alternative for the other need: fetch full text with `get_post`. This is explicit when-to-use plus named alternative.

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