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

The annotations declare openWorldHint=true and readOnlyHint=false, but the description says there is no provider and calls return a not-implemented notice. This contradicts the annotations' implication of external access and side-effect potential. Per the rules, a description that contradicts annotations scores 1.

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 key warning is front-loaded, but the description repeats the same fact (placeholder, not live, not implemented) across multiple sentences. It could be reduced to one sentence without losing information.

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 placeholder with no output schema, the description sufficiently states what calls return (a not-implemented notice) and that no provider exists. It could be more complete by explicitly directing the agent to a functional alternative, but it is largely adequate for the tool's limited purpose.

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% for the single 'input' parameter, and the schema already explains it as a capability-specific payload. The description adds no additional parameter meaning, so this is the baseline 3.

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 explicitly states this is a placeholder web-search slot with no provider and that calls return a not-implemented notice. This clearly distinguishes it from functional siblings like search and fetch, so an agent can immediately tell it is not a usable web search tool.

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 clearly establishes when not to use the tool: it is not live, not implemented, and has no provider behind it. However, it does not explicitly name an alternative (e.g., 'use search instead'), although the implied alternative is obvious from the sibling context.

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