list_my_board_tasks

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

No annotations are provided, so the description bears the full burden of disclosure. The statement 'List all tasks' conflicts with the maxResults parameter (default 50), which caps the returned count. It also omits details like pagination, ordering, or return format, creating uncertainty about actual behavior.

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 core description is concise and front-loaded. The second clause 'Use terminal commands for board-specific searches' is brief but ambiguous, adding a potential source of confusion rather than clarity.

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 exists, so the description should clarify what is returned (e.g., task IDs, titles, statuses). It does not, and the phrase 'all tasks' is misleading given the maxResults cap. The tool is simple, but the missing output details and internal inconsistency make it incomplete.

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?

The only parameter (maxResults) has a complete schema description ('Maximum number of results to return'), so the tool description adds no new semantic value. Baseline of 3 is appropriate for full schema 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?

Clearly states the action (list), the target (all tasks assigned to current user), and the scope (CCOE project board Atlantis P&D). This distinguishes it from sibling tools like list_my_tasks which likely cover all 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?

Implies board-specific use and explicitly advises using terminal commands for board-specific searches, providing an exclusion criterion. However, it does not explicitly compare with sibling list tools like list_my_tasks or list_in_development, so guidance is only partially complete.

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