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

No annotations are present, so the description must carry safety and behavior disclosure. It states that this is a compatibility tool for remote MCP retrieval flows, but does not explicitly confirm read-only behavior, error handling, or return format. The description adds minimal behavioral context beyond the tool's name and title.

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?

Two sentences, front-loaded with the core action, no redundant filler. Every word earns its place.

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 one-parameter tool with no output schema, the description provides adequate context: it identifies the predecessor (search) and the target use case. It could mention return behavior but isn't critically missing for this simple tool.

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 input schema covers 100% of the parameter with description, and the tool description adds no additional parameter semantics. Baseline 3 applies.

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 uses a specific verb ('Fetch') and identifies a resource ('specific result returned by search'), distinguishing it from search tools and the sibling fetch_research_url. It also explains why this tool exists, as a compatibility shim for OpenAI/ChatGPT MCP flows.

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?

It explicitly frames this as a compatibility tool for OpenAI/ChatGPT remote MCP retrieval flows, giving clear when-to-use context. It doesn't name alternatives or exclusions, but the usage context is reasonably clear.

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