run_saved_query

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

With no annotations, the description carries the full burden. It describes the basic operation but fails to disclose whether the tool is read-only, idempotent, or how it handles errors like invalid query IDs. No side effects or limitations are mentioned.

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 concise with two sentences and a bulleted args list. No unnecessary information, and the purpose is front-loaded.

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 low complexity (2 params, output schema exists), the description is minimally viable. It covers purpose and parameters, but lacks behavioral details that an agent might need, especially without annotations. It could be more complete.

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 description adds meaning by explaining 'project' as an Azure DevOps project name with a default, and 'query_id' as a saved query GUID. Since the schema has 0% description coverage, this is valuable, but does not specify how to find the GUID or validate it.

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 executes a saved query and returns work item details. The verb 'execute' and resource 'saved query' are specific, but it does not explicitly differentiate from sibling tools like 'query_work_items' which might run inline queries.

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 over alternatives. There is no mention of prerequisites, such as needing a saved query GUID obtained from 'list_saved_queries', or when to use inline queries instead.

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