search_copilot

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions a timeout parameter with a default value, which is useful context about potential delays. However, it doesn't describe what the search returns (web results, AI responses, documents), authentication requirements, rate limits, error conditions, or any other behavioral characteristics. For a search tool with no annotation coverage, this is insufficient.

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 - just two sentences that directly state the tool's purpose and parameters. It's front-loaded with the main purpose and wastes no words. However, given the complexity of the tool and lack of other documentation, this brevity might be too minimal rather than appropriately sized.

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 (search functionality with Microsoft Copilot), the lack of annotations, no output schema, and the presence of many similar sibling tools, the description is incomplete. It doesn't explain what kind of search results to expect, how results differ from other search tools, or any operational constraints. The description should provide more context to help an agent use this tool appropriately among the many alternatives.

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 explicitly lists both parameters ('query' and 'timeout') and provides some semantic information about timeout being in seconds with a default of 90. However, the schema description coverage is 100%, meaning the schema already documents both parameters thoroughly. The description adds marginal value by explicitly calling out the parameters, but doesn't provide significant additional semantic context beyond what's in the schema.

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 'Microsoft Copilot search' which indicates the tool performs search functionality using Microsoft Copilot. However, it doesn't specify what type of search (web, document, enterprise, etc.) or what resources are being searched. The description is somewhat vague compared to sibling tools like 'search_bing_search' or 'search_google_search' which are more specific about their search targets.

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 the many other search tools available on the server. With 12 sibling search tools including Bing, Google, ChatGPT, Claude, and others, there's no indication of what makes Microsoft Copilot search distinct or when it should be preferred over alternatives. The description offers no usage context or exclusions.

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