Get a board

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds that it fetches a single board and includes optional includes, but does not elaborate on behavioral traits beyond what annotations provide. No contradiction.

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 well-structured with a header, args list, and example. It is front-loaded with the main purpose. However, the Args list largely duplicates schema information, which could be more concise.

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 6 parameters (1 required) and no output schema, the description covers the essential functionality: fetching a board with optional includes and an example. It does not mention error handling or response structure beyond the format, but the parameter descriptions and example provide reasonable completeness.

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 description re-iterates each parameter with brief notes, including the default for response_format and explaining the difference between markdown and json. This adds value beyond the schema, which had only 33% description coverage. The example shows usage with an optional include.

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 clearly states 'Fetch a single board by its publicId,' which is a specific verb+resource+identifier. This distinguishes it from sibling tools like kanbanzone_list_boards (which lists all boards) and other get tools. The example reinforces the purpose.

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 a clear context for fetching a single board by publicId, but does not explicitly state when to use this tool versus alternatives such as kanbanzone_list_boards or other get tools. The name and example imply the usage, but explicit exclusions are missing.

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