router_get_system_logs

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

No annotations are provided, so the description carries the full burden. It does add real behavioral value by disclosing that force='bypasses Network Guard safety check' and that lines defaults to 50. However, it never states this is a non-destructive read, whether authentication/permissions are required, or how large result sets behave — meaningful gaps for a tool with zero annotation coverage.

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?

Front-loaded with the purpose, then an Args block that is scannable and waste-free. The list format is appropriate for four parameters and nothing is padded, though it reads as auto-generated docstring prose.

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?

A read-only log fetch with an output schema present, so return-value detail is not required, and all four parameters are documented. What's missing is the safety/permission framing that the absence of annotations would otherwise leave the description to supply.

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 0%, so the description must compensate — and it largely does: each of the 4 params gets meaning, the default for lines, example values for module, and the full severity enum for min_level, none of which appear in the schema. Only minor gaps remain (module has no closed value list, lines has no upper bound).

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?

States a specific verb and resource: 'Retrieves system and cellular event logs from the TP-Link router.' That cleanly separates it from the sibling router_clear_system_logs, though the contrast is left implicit rather than stated. An agent can identify what it does without opening the schema.

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 filter parameters imply the intended usage (narrow by module or severity), but the description never says when to reach for this tool, when not to, or which sibling to use instead (e.g., for a status snapshot use router_get_status). Usage is inferable but not guided.

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