route_table

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

No annotations are provided, so the description must carry the full behavioral burden, yet it omits that this is a read-only, no-argument, local-host query and that it returns nothing about remote targets. It does at least scope the data to 'the computer's' own table rather than a remote host, which is a meaningful constraint.

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?

A single short sentence with zero filler, front-loaded on the resource. Its brevity flirts with under-specification rather than waste, but nothing in it fails to earn 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?

With zero parameters and an output schema covering return values, the bar is low, and the description adequately identifies the data. However, for a diagnostic toolset this dense, it leaves the agent without a reason to pick this over ip_config or arp_table.

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 takes zero parameters, so the baseline is 4; there is nothing for the description to explain and it correctly implies no inputs are needed.

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 names the resource (the routing table) and adds one substantive detail (default route 0.0.0.0/0), but it is a noun phrase with no verb, so the action (retrieve/display) is only inferred. It never contrasts itself with the adjacent siblings ip_config or arp_table, which an agent could easily confuse with routing information.

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?

There is no guidance on when to call this versus ip_config, arp_table, or traceroute, and no mention of prerequisites or context. The agent must infer usage purely from the tool name.

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