router_clear_system_logs

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

With no annotations, the description carries the full burden. It usefully discloses the confirm safety gate and that force bypasses a 'Network Guard safety check,' which is real behavioral context. It omits the critical point that clearing logs is irreversible and does not say what the response contains or whether confirmation is required despite required_parameters being 0.

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 definition is short and front-loaded, with the core action in the first sentence and parameter meanings in a compact Args block. The parameter lines restate names but earn their place because the schema has no descriptions.

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 two-boolean destructive operation, the definition covers the safety flags but omits irreversibility and prerequisites. An output schema exists, so return values need not be explained, but the destructive nature of the operation should be explicit.

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 description coverage is 0%, so the description must compensate — and it does, explaining confirm as a safety confirmation to clear logs and force as a bypass for the Network Guard safety check. It does not clarify how the two flags interact, such as whether force alone clears logs without confirm.

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 gives a specific verb and resource: 'Clears the internal system event log buffer on the router.' That is unambiguous. However, it never mentions the sibling router_get_system_logs, so the agent gets no explicit differentiation between reading and clearing logs.

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 purpose implies when the tool is used, and the Args section explains that confirm must be True to proceed. But there is no explicit guidance on when to prefer router_get_system_logs instead, no note that this is destructive, and no indication of what happens if force is used without confirm.

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