get_logs

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the level default, but says nothing about the 20-entry cap, whether results are truncated, or how "latest" is ordered — modest added value beyond the structured fields.

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 one-sentence purpose followed by two short, concrete examples that double as intent signals for Sonarr/Radarr phrasing. No filler, though the examples could have been spent on the undocumented limit parameter instead.

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?

An output schema exists, so return values need not be explained, and the service filter is covered by the schema. The remaining gap is the unspecified result cap/pagination behavior, which is minor for a simple read-only log fetch.

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 only 33% — the `service` parameter is documented in-schema, while `level` and `limit` rely on enums/defaults alone. The description compensates for `level` by stating the default is errors, but adds nothing for `limit` or its 1–200 range, leaving the coverage gap only partly filled.

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 ("Latest log entries") plus the scoping dimension ("at the given level") and the default. An agent can tell this apart from siblings like get_health or get_system_status, though the description never explicitly contrasts them.

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 two example queries ("Show me Sonarr's recent errors", "Why is Radarr failing? check the logs") imply a troubleshooting use case, which is useful context. However, there is no explicit when-to-use/when-not guidance and no named alternative such as get_health or diagnose_import for diagnosing failures.

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