timps_network_medic

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

With no annotations, the description carries the burden. It discloses the generation of a fix script with specific commands (DNS flush, WiFi reset, DHCP renewal), which is a significant behavior. However, it doesn't clarify whether the script is auto-executed or just generated, and potential side effects (e.g., network disruption) are not mentioned.

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 concise sentences covering both diagnostic actions and the output (fix script). No filler, front-loaded with the primary purpose.

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?

Given the single optional parameter and no output schema, the description covers the main actions and the delivered artifact. Minor gap: doesn't mention prerequisites (e.g., admin rights for network changes) or whether the script is meant to be reviewed before running.

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 coverage is 100% for the single parameter 'target' with a clear description and default. The description mentions ping/traceroute which implicitly relates to the target, but adds no additional meaning beyond the schema.

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 specific verbs and resources ('Diagnose network problems: ping internet/Cloudflare, traceroute, open ports') and clearly distinguishes itself from sibling tools by focusing on network diagnostics with a concrete fix-script generation outcome. It's unambiguous and actionable.

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 implies when to use it (network issues) but doesn't explicitly say when not to use it or compare to siblings like timps_full_checkup or timps_environment_doctor. No exclusions or alternative recommendations are provided.

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