adtk

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

With no annotations provided, the description carries full burden for behavioral disclosure. It lists actions but doesn't explain what each action does, what permissions are required, whether operations are read-only or mutating, what happens on errors, or what the expected output format is. For a tool with 7 parameters and multiple action types, this is inadequate.

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 - a single sentence listing the actions. While efficient, it may be too terse given the tool's complexity. The structure is front-loaded with the core purpose, but lacks elaboration needed for a multi-action tool.

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?

For a tool with 7 parameters, multiple action types, no annotations, and no output schema, the description is incomplete. It doesn't explain what each action returns, how actions differ in behavior, what authentication or permissions are needed, or how this tool fits within the broader Azure DevOps context alongside its many sibling tools.

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%, so the schema already documents all parameters thoroughly. The description adds minimal value by listing the action names, but doesn't provide additional context about parameter relationships, constraints, or usage patterns beyond what's in the schema descriptions.

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 the tool manages Azure DevOps iterations (sprints) and lists the specific actions available, providing a specific verb ('manage') and resource ('iterations'). However, it doesn't differentiate this tool from its many sibling 'manage_' tools that handle different Azure DevOps resources.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when to choose specific actions, or how this tool relates to sibling tools like manage_work_items or manage_boards that might handle related concepts.

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