get_project_board

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the output is a point-in-time snapshot grouped by columns, which is useful context. It does not mention pagination, limit, or archived-item behavior, but those are partially reflected in the schema defaults.

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?

A single sentence that front-loads the key behavior and grouping. It contains no filler and does not duplicate schema or annotation details.

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 simple read-only board reader with an output schema and annotations, the description is workable but leaves the agent to infer usage context and parameter semantics. The missing guidance on when to use it and what include_archived means prevents it from being fully self-contained.

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 0% and the tool description does not mention project_id, limit, or include_archived. The parameter names are fairly self-explanatory and the schema provides types and defaults, but the description fails to clarify the effect of include_archived or limit.

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 states a clear verb ('Return') and resource ('planning snapshot grouped by Kanban columns'), and names example columns ('Backlog/In Progress/etc.'). It conveys a board-level read distinct from task-level tools, though it does not explicitly differentiate from siblings like list_tasks or get_project_workload.

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 guidance is given about when to use this tool versus alternatives such as get_project, list_tasks, or get_project_workload. The read-only nature and column grouping imply a board-overview use case, but the description never states when it should be preferred.

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