adtk

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It lists action names but doesn't explain what each action does, their effects, permissions required, rate limits, or error conditions. For a tool with 18 parameters and multiple mutation actions (create, update, vote, etc.), this is a significant gap in 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 a single, efficient sentence that lists all available actions. There's no wasted space or redundant information. However, it could be better structured by grouping related actions or providing a brief overview before the list.

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 complex tool with 18 parameters, multiple mutation actions, no annotations, and no output schema, the description is inadequate. It doesn't explain what the tool returns, how actions differ, what permissions are needed, or provide any behavioral context. The description fails to compensate for the lack of structured metadata.

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 18 parameters thoroughly. The description adds no parameter information beyond what's in the schema - it doesn't explain relationships between parameters, provide examples, or clarify dependencies. The baseline of 3 is appropriate when the schema does all the heavy lifting.

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 states the tool manages Azure DevOps pull requests and lists actions, but it's essentially a tautology that restates the tool name ('manage_pull_requests') with a list of verbs. It doesn't specify what 'manage' entails or distinguish this tool from its many siblings (e.g., manage_work_items, manage_repos). The description lacks a clear, specific purpose statement.

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?

There is no guidance on when to use this tool versus alternatives. With 13 sibling tools on the server, the description provides no context about when this pull request management tool is appropriate versus other tools like manage_work_items or manage_repos. No prerequisites, constraints, or comparison to alternatives are mentioned.

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