list_boards

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

No annotations provided, so description carries full burden. States it is a read-only listing operation. Mentions output fields (workspaceId, spaceId) but lacks details on permissions, pagination, or side effects.

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 succinct sentences with no wasted words. Every sentence adds value: purpose, filter capability, output hint.

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?

No output schema and no annotations. Description covers basic listing and filtering but omits details on pagination, ordering, other possible fields, or limits. Adequate for a simple list but leaves gaps.

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 0% but description adds meaning by explaining that workspaceId and spaceId serve as optional filters and that each board includes these IDs in the response. This provides context beyond the plain 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?

Clear verb+resource combination ('List boards'). Mentions filtering by workspaceId/spaceId and that each board includes those IDs, which distinguishes it from sibling tools like list_cards or list_spaces.

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?

Implies usage context (filtering by workspaceId/spaceId) but provides no explicit guidance on when to use vs alternatives like list_workspaces or list_spaces. No when-not conditions stated.

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