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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds the precondition that the list must have been previously deleted, which is useful behavioral context, but does not disclose details such as what exactly gets restored, failure behavior for active lists, or permission requirements.

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 front-loaded sentence with no filler or repetition. Every word earns its place and the core operation and precondition are communicated efficiently.

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 operation with no output schema, the description is nearly complete: it names the action, the target resource, and the precondition. Minor gaps such as exact side effects and error behavior exist, but annotations already cover idempotency and non-destructiveness, so the missing detail is not critical.

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 the baseline is 3 even without additional parameter details in the description. The tool description adds the implication that list_id must refer to a previously deleted list, but it does not elaborate on ID format or how to obtain the ID, which is acceptable for a single obvious 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 specific verb (Restore) and resource (previously deleted list), clearly distinguishing this from sibling tools like create_list, get_list, and delete_list. The phrase 'previously deleted' adds essential scope beyond what the name alone conveys.

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 gives clear context by specifying that this operation applies to a previously deleted list, implying it should be used rather than create_list when undoing a deletion. It does not explicitly name alternatives or when-not-to-use conditions, but the single-sentence scope is sufficient for this straightforward operation.

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