flush_route_cache

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

Annotations already declare destructiveHint=true, but the description adds no behavioral detail beyond that. It does not explain the operational impact (e.g., clearing cached routes may disrupt active sessions), whether it requires confirmation, or what happens on failure. The description contributes no additional transparency beyond the 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 a single, direct sentence that immediately states the action. It is economical and well-structured with no redundant content.

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?

This is a simple tool with one optional parameter and an output schema. The minimal description is sufficient for basic invocation, and annotations cover destructive behavior. However, it lacks context about when to flush the cache, prerequisites, or potential side effects, making it incomplete for a full 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?

The schema has one optional parameter 'device' with 0% description coverage. The description does not mention this parameter at all, so it adds no meaning beyond what the schema already provides (device name, default null). For a low-coverage case, the description should have explained the parameter usage but fails to do so.

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 is clear and specific: 'Flushes the route cache.' It uses a strong action verb and a precise target resource, distinguishing it from sibling tools like get_route_cache (read) and flush_dns_cache (DNS vs route).

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 gives no guidance on when to use this tool, when not to use it, or alternatives. It merely states the action without any context about route cache invalidation, device targeting, or relationship to other route tools.

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