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

Annotations already declare readOnly, idempotent and non-destructive. The description adds real value beyond them by disclosing that title, folder/item names, notes, people and trail label are free text supplied by the list's editor and are returned unchanged, which is meaningful context about untrusted content the caller will receive.

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, front-loaded with the output format before the input and content-fidelity note. Slightly dense but no filler; every clause carries information.

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?

No output schema exists, so the description carries the return-value burden and does so by describing the Markdown structure (per-folder tables, totals block). Combined with the annotations and a single fully documented parameter, an agent has enough to call it correctly; only the explicit sibling relationship to get_list 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 coverage is 100% and the description's 'Takes a share code or share link' merely restates what the schema already documents, including the edit-link exclusion. With one parameter fully described in the schema, the description adds no syntax beyond it.

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?

The description names a specific resource and output form: the shared list rendered as Markdown with 'one table per folder and a totals block.' The phrase 'The same list as Markdown' implies the sibling get_list returns the same data in a different form, though it never names that alternative explicitly, keeping this short of a 5.

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?

Usage is implied rather than stated: the agent can infer this is the tool for a Markdown-format export versus get_list's presumably structured output. There is no explicit when-to-use/when-not statement and no naming of alternatives.

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