List board items

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

Description mentions pagination with a `hasMore` flag but does not disclose side effects, permissions, or error behavior. With no annotations, the description carries the burden but provides only partial transparency.

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 sentences, front-loaded with purpose, no redundancy. Efficient and clear.

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?

Lacks details on response format (beyond hasMore), how filtering works, or interpretation of results for 8 parameters. Adequate but not fully complete for a list tool with many options.

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 has 100% parameter coverage with descriptions, so the description adds minimal new meaning beyond summarizing 'optional filtering' and 'pagination'. Baseline 3 is appropriate.

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?

The description clearly states it lists items on a board with optional filtering and pagination. It distinguishes itself from sibling tools like plaky_create_item, plaky_get_item, etc. by focusing on listing all items.

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?

No explicit guidance on when to use this versus alternatives (e.g., plaky_get_item for a single item, plaky_list_subitems for subitems). The description implies usage for listing but lacks when-not-to or context for other tools.

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