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

Annotations already declare readOnlyHint=true, so the description is not required to restate that. It adds valuable behavioral context: the return format (markdown with title, items, notes, links), the accepted input forms (URL pattern or bare id), and the strict privacy constraint. No contradictions with 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?

The description is a single, well-structured sentence that front-loads the core action and resource, then adds the input format and a key constraint. Every word earns its place; there is no fluff or repetition.

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 single-parameter read tool with no output schema, the description fully covers what the tool returns, how to specify the input, and the privacy limitation. Annotations cover the read-only nature, so nothing an agent needs to correctly call 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 coverage is 100% with the param description 'List URL or id', but the tool description enriches this by specifying the exact URL format (https://www.listdrop.co/l/<id>/…) and explicitly confirming that a bare id is accepted. This goes beyond the schema and leaves no ambiguity about how to construct the parameter.

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 states a clear verb ('Returns') and a specific resource ('PUBLIC ListDrop list as markdown'), and specifies the input format (URL or bare id). It also distinguishes itself from siblings by explicitly limiting to public lists, while create_list and my_lists clearly cover other operations.

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?

The description clearly indicates when to use this tool (for public lists) and explicitly excludes private lists with 'Private lists are never readable.' While it doesn't name the alternative for private lists (my_lists is implied), the exclusion is explicit enough for an agent to infer the correct usage boundary.

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