azdo_list_team_boards

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List boards' implies a read-only operation but does not specify any behavioral traits such as pagination, rate limits, authentication needs, or what data is returned. This is inadequate for a tool with 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?

While concise with only two words, the description is under-specified rather than efficiently informative. It fails to front-load critical details and does not earn its place by adding value beyond the tool name, making it ineffective despite its brevity.

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 lack of annotations and output schema, the description is incomplete. It does not explain what 'boards' entails, the return format, or any operational constraints. For a tool with three required parameters and no structured behavioral hints, this minimal description leaves significant gaps for an AI 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 clear descriptions for all three parameters (organization, project, team_id). The description adds no additional meaning beyond the schema, but the high coverage justifies a baseline score of 3, as the schema adequately documents the parameters.

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 boards' is a tautology that restates the tool name 'azdo_list_team_boards' without adding meaningful context. It lacks specificity about what type of boards (e.g., Azure DevOps team boards) or what scope (e.g., for a specific team) is involved, which is minimally addressed by the tool name but not elaborated in the description itself.

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. Sibling tools like 'azdo_get_team_board' (singular) and 'azdo_list_teams' exist, but the description does not differentiate this tool's purpose or specify prerequisites, leaving the agent without context for selection.

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