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

Annotations already declare readOnlyHint/openWorldHint=false/destructiveHint=false, so safety is covered structurally. The description adds real context the annotations don't: newest-first ordering, default hiding of archived sheets, and the tab/chart counts returned. Return format detail (pagination, exact shape) is still absent.

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 tight sentences with zero filler; the resource definition and default scoping come first, then the parameter effects, then the next-step routing. 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?

For a read-only listing tool with full schema coverage and no output schema, the description supplies the return ordering and summary fields an agent would otherwise guess at, plus the workflow handoff to schema/query. Only pagination or result-size expectations 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?

Schema description coverage is 100%, so all three parameters are already documented in the schema, including the workspace-slug auth nuance. The description restates `includeArchived` and `q` behavior without adding syntax or format detail beyond the schema.

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 workspace's Napkin sheets), and even defines the resource ('multi-tab spreadsheets — the small-data surface'), distinguishing it from sibling surfaces like boards, docs, and diagrams. The sort order and returned summary fields (tab/chart counts) are front-loaded.

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 explicit behavioral context ('Archived sheets are hidden unless `includeArchived`; `q` narrows by title') and names the follow-up path (napkin_sheets_schema to inspect, napkin_sheets_query to query). It lacks any explicit when-not-to-use guidance (e.g., vs search_workspace or napkin_docs_list), so it falls short of a 5.

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