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

Goes well beyond the annotations (readOnly/idempotent/non-destructive/closed-world): it discloses that trashed boards are excluded, the exact result ordering (canvas top-to-bottom, then Unsorted), the returned fields, and that parent_board_id in the response is Home's id when omitted. These are the details an agent needs to reason about traversal results without trial and error.

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 statement and the nesting model, and every later sentence adds a distinct fact (ordering, echo behavior, trash exclusion). The first two sentences overlap somewhat, restating the one-level-down/Home scope, which is minor redundancy rather than bloat.

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?

With no output schema, the description correctly compensates by naming the returned fields and the ordering, and it covers the trash filter. The only gap is pagination behavior: limit is capped at 200 but the description doesn't say whether results can be truncated or how to continue past the limit.

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 real meaning: parent_board_id is a traversal control that yields the next level down, and its effective value is echoed in the response. The limit parameter is left entirely to the schema ('1 to 200. Default: 50'), which is acceptable given full coverage.

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 (lists) and resource (boards) with a precise scope: exactly one level down, either Home or inside parent_board_id, returning title, ID and link. The folder-nesting analogy makes the hierarchical semantics unambiguous. It never names the sibling it competes with (search_boards, list_recent_boards, get_board), so differentiation is inferential rather than explicit.

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?

Gives clear operational guidance: omit parent_board_id for Home, pass a board's id to walk down a level. It also explains that the answer echoes the effective parent_board_id, which tells the agent how to keep track during traversal. No explicit exclusions or pointers to alternative tools for finding boards by name or recency.

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