opnsense_diag_log_routing

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Retrieve... log entries,' implying a read operation, but does not specify whether logs are paginated, how errors are handled, or any rate limits. The limit parameter suggests pagination but is not explained.

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 sentence that directly states the purpose, followed by an implicit parameter note. It is front-loaded and free of unnecessary words. However, it could be slightly expanded without being verbose.

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 tool has only one parameter and no output schema, the description covers the basic purpose but lacks usage guidelines and behavioral details. It does not help the agent differentiate from sibling log tools, which is a gap for a diagnostic tool in a set of similar tools.

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 100%, with the single parameter 'limit' already documented (number, range 1-5000, default 500). The tool description adds no further meaning beyond the schema, so baseline score of 3 is appropriate.

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 clearly states the tool retrieves recent OPNsense routing daemon log entries. The verb 'Retrieve' and resource 'routing daemon log entries' are specific, and it distinguishes from sibling tools like opnsense_diag_log_system or opnsense_diag_routes by focusing on routing daemon 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 description provides no guidance on when to use this tool versus other diag log tools (e.g., opnsense_diag_log_gateways, opnsense_diag_log_resolver). There is no mention of typical use cases or exclusions, leaving the agent to infer context solely 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.