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

Annotations already declare the safety profile (readOnly, idempotent, non-destructive), so the description's job is to add behavioral context — which it does: deterministic newest-first ordering and the fact that the response also carries the available topic list. It omits pagination/limit truncation behavior, which is the remaining gap.

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?

A single tight sentence pair: what is listed, in what order, what fields, then the optional filter. Ordering and scope are front-loaded and nothing is wasted.

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?

With an output schema present, the description need not detail return values, yet it still names them, and it covers filtering and ordering. The only missing piece for correct invocation is any hint about result-set size or the limit default.

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%, so the schema already documents both limit and topic. The description only echoes the topic filter and never mentions the limit parameter or its default, so it adds little beyond the structured fields — the 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?

States a specific verb and resource ('List the essays'), plus ordering ('newest first') and the fields returned, so the agent knows exactly what comes back. It does not explicitly contrast itself with the sibling get_essay, so it falls short of the 5 bar for sibling differentiation.

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?

'Optionally filter by topic slug' implies the filtering use case, and 'Omit for all essays' in the schema reinforces it. However, there is no explicit guidance on when to use this versus get_essay (single essay) or search, leaving selection to inference.

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