devops_code_search

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 mentions returning snippet context but does not disclose rate limits, authentication needs, or pagination behavior beyond what's in the schema. The behavior is adequate for a straightforward search tool.

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 two sentences, front-loaded with the primary action, and contains no unnecessary words. Every sentence adds value.

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 tool's complexity (7 parameters, output schema exists), the description covers the main purpose and return type ('snippet context'). It does not explain the output schema but that is acceptable since the schema is provided. Minor omission: it doesn't mention the required parameter 'search_text' explicitly, but the schema covers it.

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 baseline is 3. The description adds minimal value by listing a few parameters ('repository, path, and branch') that are already detailed in the schema. No additional meaning or examples are provided.

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 action ('Search source code') and the resource ('configured Azure DevOps project'), and specifies the return type ('matching file locations with snippet context'). It distinguishes from sibling tools like devops_work_item_search and devops_wiki_search by focusing on source code.

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 implies usage for querying source code and lists optional filters, providing clear context. However, it does not explicitly state when not to use this tool or compare it to alternatives, so a 4 is appropriate.

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