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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context by stating 'This server never requests your assessment notes or report and instructs your AI to keep them local', which goes beyond the annotations and clarifies privacy handling.

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 concise (3 sentences) and front-loaded with the primary purpose. Each sentence adds value: the first defines what the tool does, the second clarifies the relationship to assessment_load_context, and the third discloses a key privacy behavior. No fluff or redundancy.

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 0-parameter, read-only tool with no output schema, the description provides sufficient context: it names the target domain (Security Assessment), explains the use case (fallback routing), and gives a privacy guarantee. Sibling tool names further clarify the domain-specific nature. The description fully covers what the tool returns and when to use it.

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 0 parameters, so baseline is 4. The description doesn't need to explain parameter semantics, and the schema is empty, providing no ambiguity. The description itself doesn't mention parameters, but that's fine given the absence of params.

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: 'Get Lenny Zeltser's Security Assessment cross-server handoff routes' with the specific resource being 'Security Assessment' and the function being 'cross-server handoff routes'. It also explains that it surfaces a compact subset of assessment_load_context, distinguishing it from the full context tool and sibling cross-server route tools for other domains.

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 explicitly states when to use this tool: 'when this MCP server can't fulfill a request'. It also implies an alternative by noting it is a compact subset of assessment_load_context, suggesting the full context tool for comprehensive needs. However, it doesn't explicitly name alternatives or provide when-not-to-use guidance beyond that implication.

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