board_summary

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

Since there are no annotations, the description defines the primary behavioral trait—that it provides a holistic overview of task statuses and sprint progression. This is useful context for a summary function.

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 extremely brief and avoids any superfluous wording, using a single sentence to convey the comprehensive function of the tool.

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?

The definition is highly complete given the lack of parameters. However, it falls slightly short because it does not provide context on whether this view is read-only or if there are restrictions on the board it summarizes.

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?

With zero parameters, the description does not need to add semantic meaning beyond what the schema provides. The baseline score for zero parameters is 4, and this description is a single, concise sentence.

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 provides a detailed breakdown of the result ('Board name, task counts per status, and every sprint with its progress'), which clearly defines the scope and content of the function.

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?

While it describes the output, it offers no guidance on when this tool should be used compared to other monitoring tools like check_board or list_tasks, making decision-making for the agent difficult.

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