azdo_list_board_columns

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

No annotations are given, so the description bears full responsibility. It only states 'List board columns' without disclosing read-only nature, potential errors, or any side effects. This is insufficient for behavioral transparency.

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 (3 words), which is efficient but sacrifices necessary detail. It is front-loaded but fails to provide any context beyond the name. It earns a 3 for being minimally adequate.

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 4 required parameters, no output schema, and no annotations, the description is incomplete. It lacks information about return values, pagination, or behavior. More detail is needed to fully guide 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?

The input schema has 100% description coverage for its 4 parameters, so the baseline is 3. The description adds no additional meaning beyond what the schema already provides, resulting in a neutral score.

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' clearly states the verb (list) and resource (board columns), distinguishing it from siblings like azdo_list_board_rows or azdo_list_team_boards. However, it does not elaborate on the specific board context, so it's not a 5.

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 usage guidelines are provided. The description does not suggest when to use this tool versus alternatives, nor does it mention prerequisites or context. This leaves the agent with no guidance for correct invocation.

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