Tail allowlisted Hermes log

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds behavioral context about 'bounded reads' and 'redaction' behavior, plus the allowlist restriction that governs access. However, it doesn't disclose what happens on denied paths (error? empty output?) or the return format details despite having an output schema.

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 packs purpose, constraints, and exclusions. No wasted words. The 'configured allowlisted' qualifier plus 'bounded reads and redaction' plus 'arbitrary log paths are denied' conveys the full operational contract economically.

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?

With 6 parameters, 0% schema coverage, an output schema present, and readOnly/idempotent annotations, the description provides the core security contract (allowlisted only) but doesn't explain several parameters (home, profile, toolkit_root) or how a user determines which log_name values are valid. The output schema exists so return values don't need description, but param guidance and log discovery are incomplete for a 6-param tool.

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 0%, so the description carries the burden. However, it only adds meaning for the overall operation (bounded reads/redaction) without explaining individual parameters. The schema already documents defaults (lines=80, max_bytes=65536) and constraints (max 500 lines, 1MB), but the description doesn't clarify what log_name must match or how to find valid allowlisted log names.

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 uses a specific verb ('tail') plus resource ('configured allowlisted log path') and adds scoping constraints ('bounded reads', 'redaction'). It distinguishes from siblings since the 'allowlisted' restriction makes clear this is not a generic file-reading tool. However, it doesn't explicitly reference sibling differentiation or describe what 'Hermes log' means concretely.

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 states when the tool is usable: 'configured allowlisted log path' and explicitly says 'arbitrary log paths are denied,' providing a clear exclusion criterion. It implies the alternative (that arbitrary paths aren't allowed and you must use allowlisted ones) without naming specific sibling tools. This gives reasonable context for when to use vs not use.

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