get_recent_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 discloses that output is ANSI-stripped and that an hb-service install is required, which are useful behavioral details. Minor gaps like output format (array vs. string) or behavior on empty logs are not critical for this simple tool, so a high score is warranted.

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?

Two sentences with the core function front-loaded in the first sentence and the prerequisite in the second. No wasted words, perfectly concise and well-structured.

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 simple tool with one optional parameter and no output schema, the description covers essential functionality and the key constraint. It does not explicitly mention the output type (e.g., array of lines), but that is likely inferable. The lack of differentiation from search_logs is a minor gap, so not a 5 but solid.

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 schema describes the single 'lines' parameter with default, min, max, and a clear description, achieving 100% coverage. The description adds no extra meaning about the parameter, so it stays at the baseline for schema-covered parameters.

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 verb 'Return' and the resource 'the most recent lines from the Homebridge log', with the specific detail of ANSI-stripping. It is distinct from siblings like search_logs (which implies search), and from status/config tools, leaving no ambiguity about what this tool does.

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 a clear prerequisite ('Requires an hb-service based Homebridge install') but does not explicitly state when to choose this tool over alternatives like search_logs. It implies usage for fetching recent log output, but lacks any when-not-to-use guidance or explicit alternative mentions.

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