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

Annotations already cover read-only, idempotent, and closed-world behavior, so the redundant 'Read-only' sentence adds little. What does add value is the disclosure of ordering (newest first), scope (signed-in user only), and the per-item field set including a details link, which an agent cannot infer from annotations.

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 well-formed sentence front-loads the resource and ordering, then enumerates returned fields compactly. Nothing is wasted and there is no filler.

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 one-parameter read-only listing tool with no output schema, the description supplies the return shape (title, status values, language, details link) and ordering, which is exactly what the missing output schema would otherwise need to cover.

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?

There is only one optional parameter (limit) and schema description coverage is 100%, with the default of 10 already documented in the schema. The description adds no syntax or behavioral detail about limit, so 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 (Lists) and resource (the signed-in user's most recent Novelist novels) plus scope, ordering, and returned fields. This clearly separates it from get_novel_status, which fetches status for one novel, and from the prepare/get_novel_options siblings.

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?

Implies the tool is the entry point for browsing a user's novels and notes the 'signed-in user' scope, which hints at an auth prerequisite. However, it never explicitly says when to use this versus get_novel_status or get_novel_options, and gives no exclusions.

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