list_boards

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

No annotations exist, so the description carries the full behavioral burden. It discloses sort order ('newest first'), which is genuinely useful, but says nothing about the default limit, whether results are paginated or capped, or what a board record contains—all behavior an agent must know before calling a list tool.

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?

Two short sentences, zero filler, with the core purpose and ordering front-loaded and the sibling routing placed second. Every clause earns its place.

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 one optional parameter, no output schema, and no annotations, the surface area is small, so the terse description is close to adequate. Still, an agent cannot tell what the default page size is or how much data comes back, which matters for a listing call whose main risk is unbounded results.

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 0%: the single 'limit' parameter has only min/max bounds and no prose. The description never mentions limit at all—not its default value, not whether omitting it returns all boards or a capped page. The one parameter present is therefore undocumented in both places.

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 ('List saved boards') plus the ordering ('newest first'), and explicitly distinguishes itself from the sibling show_board, which retrieves a single board by id. An agent can pick between the two 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?

The second sentence names the alternative (show_board with an id) and the condition that selects it, so the list-vs-retrieve fork is covered. It stops short of stating when not to use this (e.g., when an id is already known, skip listing), so it is clear context rather than a full when/when-not rule set.

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