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

Annotations already declare this a safe, idempotent read, so the description focuses on behavior the annotations can't express: lists are snapshots that can change, a list is not a passable target, boards must be passed as intervalBoards in the returned order, and entries whose board id is missing from list_boards are stale. That stale-reference and ordering guidance is genuinely beyond structured data.

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 the 'Use this when' trigger, then the definition, then the handoff to create_post. It is dense and slightly run-on in the middle section, but nearly every clause carries operational information rather than 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?

For a one-parameter read with an output schema, this covers everything an agent needs: when to call it, what a list means, how to consume the ordered boards downstream, how to handle dangling board ids, which siblings mutate lists, and the account-selection prerequisite.

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% and the single accountId parameter is fully documented in the schema, so the baseline would be 3. The description adds real semantic guidance by tying accountId to list_accounts output and specifying a disambiguation behavior when multiple accounts exist.

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 ('lists the account's board lists') and immediately defines what a board list is ('Tailwind's named groupings of boards, used to publish one Pin to several boards in order'). This distinguishes it from sibling readers like list_boards and list_board_sections, which an agent could otherwise confuse with it.

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?

Enumerates three concrete triggering situations (user asks about lists, auditing board organization, user names a list as a Pin destination) and names the sibling mutation tools (create_board_list, update_board_list, delete_board_list) that handle list management instead. It also gives an explicit precondition: if the account is ambiguous and list_accounts returns multiple, ask the user rather than choosing.

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