azdo_list_team_members

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

With no annotations, the description fully shoulders the burden of behavioral disclosure. It only states 'List team members' without indicating permission requirements, return format, or side effects. The agent receives no insight into read-only status or other behavioral traits.

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 lacks structure or front-loading of critical context. While it doesn't waste words, it omits useful details that could fit in a compact format.

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?

The tool has 3 required parameters and no output schema. The description does not explain what the output represents (e.g., list of member names, IDs, details), nor does it clarify the scope (e.g., only active members). This incompleteness leaves the agent uncertain about outcomes.

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 coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the schema's parameter descriptions (e.g., it doesn't explain how team_id relates to the members list). It neither enhances nor harms the schema's clarity.

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 team members' conveys the basic verb-resource pair, but it lacks specificity about which team and context. Compared to siblings like 'azdo_get_team' (returns team info) and 'azdo_list_teams' (lists all teams), this tool's purpose is distinguishable but not explicitly differentiated.

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 on when to use this tool versus alternatives such as 'azdo_get_team' or 'azdo_get_team_board'. There is no mention of prerequisites, when-not-to-use, or related tools, 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.