list_boards

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

No annotations are provided, so the description carries full burden. It only says 'List all boards in a project' without mentioning key behaviors like pagination, the effect of the includeClosed parameter, or any error conditions. This is insufficient for an agent to know what happens when invoked.

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?

The description is a single sentence with no unnecessary words, which is concise. However, it is too minimal; it could include more detail (e.g., about parameters or return value) while staying concise. It is adequate but not excellent.

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?

Given the tool has two parameters, no output schema, and many sibling tools, the description is incomplete. It does not explain the return format, how to handle the includeClosed parameter, or any limitations. More context is needed for effective use.

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 only 50% (includeClosed has a description, projectId does not). The tool description does not add any parameter semantics; it does not explain what projectId or includeClosed mean beyond the schema. The description could clarify the role of projectId but does not.

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 the action ('List'), the resource ('boards'), and the scope ('in a project'). It distinguishes from sibling tools like 'get_board' which retrieves a single board. However, it could explicitly mention that it returns a list of boards.

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 description provides no guidance on when to use this tool versus alternatives (e.g., get_board for a specific board, or other board tools). No information on prerequisites or context is given.

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