azdo_list_board_columns

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a read-only operation ('List'), but doesn't disclose authentication needs, rate limits, pagination, error conditions, or what the output looks like (no output schema exists). This is inadequate for a tool with 4 required parameters and no annotation coverage.

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 concise at three words, front-loaded with the core action, and wastes no space. It could be more informative, but as a standalone statement, it's efficiently structured without redundancy.

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 the tool's complexity (4 required parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the Azure DevOps context, what 'board columns' represent, the output format, or behavioral traits like safety or side effects, leaving significant gaps for the agent.

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 100%, with all parameters clearly documented in the schema (e.g., 'Board ID or name', 'AzDO org name'). The description adds no additional parameter context beyond what's in the schema, so it meets the baseline of 3 for high schema coverage without adding value.

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 'List board columns' states the verb ('List') and resource ('board columns'), making the basic purpose clear. However, it lacks specificity about what 'board columns' are in the Azure DevOps context and doesn't differentiate from sibling tools like 'azdo_list_board_rows' or 'azdo_list_team_boards' beyond the obvious resource difference.

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 provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context (e.g., that it's for Azure DevOps boards), or relationships to siblings like 'azdo_get_team_board' or 'azdo_list_team_boards', leaving the agent to infer usage from the name alone.

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