get_sprint_board

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, which strongly covers safety and side-effect behavior. The description adds the board/column grouping context but does not disclose anything beyond that, such as how sprint names resolve or whether empty boards return an error. No contradiction exists.

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 concise, front-loaded with the main action, and every sentence earns its place. The Args list is efficient and provides necessary semantic detail without fluff. It is appropriately sized for a tool with three parameters.

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 that an output schema exists and annotations cover safety, the description is sufficient for basic invocation, but it lacks guidance for selecting this tool over similar sibling tools. It also does not state prerequisites such as whether the board must exist or what happens when the sprint is not found. These are notable gaps in an otherwise functional definition.

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%, so the Args section in the description is the sole source of parameter meaning and compensates well. It clarifies that board_name accepts a name, ID, or URL; that sprint supports the special token 'current' and defaults to it; and that instance is optional. This adds real value beyond the bare schema, though details like allowed instance formats or sprint identifier syntax are omitted.

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 specific verb and resource: 'Get issues on an agile board grouped by column.' This makes the core function clear. However, it does not distinguish from sibling tools such as get_agile_board or get_active_sprint_issues, which might also surface board/sprint issues.

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 about when to use this tool versus alternatives. It does not mention any preconditions, exclusions, or competing sibling tools. The only implied context is that it returns issues grouped by column, but that is not explicit usage guidance.

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