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

Goes well beyond the annotations by disclosing unowned-list deletion after 30 days, the secret claim URL behavior, OAuth lists:write requirements, URL-in-item linkification, view-only sharing via allowed_emails, and self-archiving via expires_in_days. These are material behavioral traits the annotations alone cannot convey, and nothing contradicts readOnlyHint=false or destructiveHint=false.

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 long but each sentence earns its place: it front-loads the core purpose and applicability, then covers account branches and optional-field behavior. The examples clarify 'list-shaped' without becoming filler.

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?

Despite having no output schema, the description explains both output variants (claim URL vs account URL) and downstream behaviors like deletion, archiving, and sharing. Given the tool's complexity and sparse schema, the description is nearly complete for correct invocation.

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?

The description adds real semantics for items (URL becomes a titled linked item) and for allowed_emails and expires_in_days. However, schema description coverage is only 29%, and the description does not explain tags, emoji, or description, so it only partially compensates for the sparse 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 ('Saves'), a resource ('ListDrop list'), and a clear scope ('list-shaped content') with concrete examples. It is easily distinguishable from siblings get_list, my_lists, and send_feedback, which read lists or send feedback instead of creating.

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?

Explicitly defines when to use the tool: when the user wants a list that outlives the conversation. It also lists exclusions ('throwaway answers, secrets or sensitive data... content that isn't list-shaped') and distinguishes the two account-state branches, giving the agent clear routing conditions.

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