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

Annotations already declare the read-only/idempotent/non-destructive safety profile, and the description goes well beyond them: it discloses truncation behavior for oversized lists (rows dropped off table ends, a line reporting how many, totals still counting every row) and warns that title, author, notes, names, brands and labels are untrusted free text returned unchanged — a genuinely valuable injection-surface signal for an agent.

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?

Front-loaded with what is returned, then input form, then the truncation caveat, then the untrusted-text note. Every sentence carries information, though the long final sentence mixing several field categories is denser than it needs to be.

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 no output schema, the description carries the return-value burden itself and does so: it describes the table-per-folder and totals structure, the exact behavior when output is truncated, and the trust level of returned text. Nothing an agent needs to call or interpret this tool 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 description coverage is 100% for the single parameter, so the schema already documents the share code / share link / not-an-edit-link semantics. The description's 'Takes a share code or share link' adds no format or syntax detail beyond that, 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 and resource ('read a list as Markdown') and immediately scopes it against the sibling get_list via 'The same list as Markdown' plus the concrete shape it returns (one table per folder, totals block). An agent can distinguish it from get_list and the catalog/trip siblings without opening any schema.

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 context is implied rather than stated: 'the same list as Markdown' and 'the text the site's own Markdown export produces' tells the agent this is the export-format variant of get_list, but it never says explicitly when to prefer Markdown over the structured sibling or when not to use it. The input guidance ('share code or share link, not an edit link') is about the parameter, not tool selection.

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