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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds substantial behavioral context beyond that: it never requests sample data, analysis notes, or indicators, and instructs the AI to keep them local. It also discloses that the tool returns a compact subset of `malware_load_context`. There is no contradiction with annotations.

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 three sentences, each with clear purpose: the first states the function, the second explains the relationship to a sibling, and the third covers privacy behavior. No filler or redundancy; every sentence 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?

Considering this is a zero-parameter, read-only tool with no output schema, the description is remarkably complete. It covers the purpose, the trigger condition (unfulfilled requests), the relationship to a related tool, and the privacy posture. There is no missing information that would hinder an AI agent from selecting and invoking this 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 tool has zero parameters and the schema is empty, so description needs to explain nothing about parameters. The per-rubric baseline for 0 params is 4, and the description does not confuse or add irrelevant parameter information.

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 the specific verb 'Get' and names the exact resource: 'Lenny Zeltser's Malware cross-server handoff routes.' It further clarifies the purpose by stating it identifies which other MCP servers to consult when the current server cannot fulfill a request, and distinguishes itself from the sibling `malware_load_context` by being a compact subset.

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 states when to use it: 'when this MCP server can't fulfill a request.' It also implies a comparison with `malware_load_context` by calling itself a 'compact subset,' suggesting that for full context one would use the other tool. However, it does not explicitly name an alternative with a direct 'use X instead' style.

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