get_project_board

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

No annotations are present, so the description carries the burden of disclosing side effects and permissions. It states the return payload (all columns, tasks, assignees, tags, subtask counts, time tracked), which implies a read-only operation. However, it does not explicitly confirm 'no changes are made' or address potential authorization or empty-board behavior. The listed fields provide partial behavioral transparency without full detail.

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, front-loaded sentence that immediately conveys action and scope. It contains no filler and every word adds value, making it very concise while still informative.

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?

For a single-parameter getter with no output schema, the description is quite complete: it names the resource, the scope ('full'), and the included components. It lacks an explicit statement about being read-only, but the 'Get' verb and board context make that implicit. The absence of annotations is not critical given the simplicity of the operation.

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 input schema describes the only parameter 'id' with 100% coverage ('The project UUID'), so the schema itself fully documents the parameter. The description adds no extra parameter detail, but none is needed given the high 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?

The description uses a specific verb 'Get' and clearly names the resource 'full kanban board for a project'. It further enumerates the board contents (columns, tasks, assignees, tags, subtask counts, and time tracked), which distinguishes it from sibling tools like get_project or get_gantt_data.

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 clearly establishes when to use the tool: when you need the complete kanban board view of a project. It does not explicitly mention alternatives or exclusions, but the context is unambiguous. A brief note about alternative views (e.g., get_gantt_data) would elevate it to a 5.

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