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

Goes beyond the annotations by disclosing duplicate behavior ('pasting it again adds only new places'), per-source limits (500 YouTube videos, notes carried in order), and the failure path for unreadable sources ('the tool says so'). Annotations cover the safety profile (openWorld, not read-only), so the description's added context is genuine value rather than repetition.

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-loads the core action and packs source support, re-import behavior, and the alternative into a tight passage. The single long sentence with nested parentheticals is dense, but nearly every clause carries actionable 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?

For a two-parameter, no-output-schema tool with annotations already declaring safety, the description covers supported sources, limits, duplicate handling, and the sibling alternative. It does not describe the immediate return (e.g. staged vs. committed picks) or how this relates to commit_import, leaving a modest gap around the import lifecycle.

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%, so baseline is 3, but the description adds meaning the schema does not: shortened maps.app.goo.gl links work, YouTube links must contain list=, and 'list' is the destination for the imported picks. This is more than restating the 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 (import picks into a list) plus the exact resources it accepts: a Google Maps shared list, a single Maps place, or a public YouTube playlist. It also names its sibling start_import and the boundary between them, so an agent can distinguish them without opening either 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?

Explicitly routes the agent to start_import for 'a whole list you want to sort first,' and warns that Spotify playlists and Letterboxd lists are no longer readable. It gives clear context but the import vs. start_import distinction is slightly fuzzy given this tool also ingests whole lists, and it never states outright when not to use the tool.

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