bing-search-to-markdown

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. While 'convert' implies a transformation operation, the description doesn't disclose important behavioral traits like whether authentication is needed, rate limits, what specific elements get converted (just text? images? links?), or error conditions. This leaves significant gaps in understanding how the tool actually behaves.

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 and front-loaded with the core functionality. The single sentence efficiently communicates what the tool does without any wasted words or unnecessary elaboration, making it easy to parse quickly.

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 lack of annotations and output schema, the description is insufficiently complete. For a conversion tool with no structured output documentation, the description should at minimum indicate what gets returned (markdown format? structure? what elements are included?). The absence of behavioral context and output information makes this inadequate for proper tool understanding.

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?

With 100% schema description coverage, the input schema already fully documents the single 'url' parameter. The description doesn't add any meaningful parameter semantics beyond what's in the schema - it doesn't clarify URL format requirements, whether the URL must be a specific Bing search results format, or any constraints on the input URL.

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's purpose with a specific verb ('convert') and resource ('Bing search results page'), making it immediately understandable. However, it doesn't differentiate from sibling tools like 'webpage-to-markdown' or 'get-markdown-file', which could cause confusion about when to use this specific tool versus alternatives.

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. With multiple markdown conversion tools available (like 'webpage-to-markdown' and 'get-markdown-file'), there's no indication of when this specific Bing-focused tool is appropriate versus general webpage conversion tools.

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