get_mikrotik_logs

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

Without annotations, the description only states the action and default limit. It does not disclose behavior on invalid identifiers, whether it's read-only, or any rate limits. The description adds minimal behavioral context beyond the obvious.

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, efficient sentence that front-loads the action. It is appropriately sized for a simple tool, though it could include a bit more detail without becoming 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 two parameters (one undocumented), no output schema, and no annotations, the description is insufficient. It does not explain what logs are retrieved, the format, or how to use the identifier. Compared to sibling tools, it lacks completeness.

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 description mentions the default limit (100 logs) but does not explain the required 'identifier' parameter, its format, or what it represents. With 0% schema description coverage, the description should compensate, but it only partially addresses one parameter.

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 it retrieves system logs with a default limit of 100, providing a specific verb and resource. However, it does not differentiate from sibling log tools like graylog_search_logs or librenms_get_device_eventlog, which might retrieve different log types or sources.

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?

No guidance is provided on when to use this tool versus alternatives like other log retrieval tools or more specific MikroTik tools. There is no mention of prerequisites, context, or exclusions.

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