tail_logs

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

With no annotations, the description carries the full burden. It usefully discloses a security behavior (allowlist enforcement, path traversal rejected), which is real value beyond the schema. However, it says nothing about error behavior on rejection, output size limits, or whether the allowlist is fixed or configurable.

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?

One compact sentence with the key constraint front-loaded and no wasted words. It is arguably over-terse for a 2-param tool, but nothing is padded.

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, which keeps the bar lower. Still, for a tool whose only parameters are undocumented, the description should cover how path is validated and how the line count is applied; those gaps remain.

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% with two parameters. The phrase 'final lines' hints at the lines parameter but never names it, gives no default behavior, and the required path parameter is only indirectly referenced via the allowlist language. Documentation of parameters is left almost entirely to the untyped schema.

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 (read) and resource (final lines of a log file) plus an important scope qualifier: one exactly allowlisted file. An agent can immediately tell this is a constrained log-reading tool, though it does not explicitly differentiate itself from siblings like health or service_status.

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 when-to-use guidance, no mention of alternatives, and no stated preconditions beyond the allowlist constraint. The diagnostic context is only implied; the agent gets no help deciding between tail_logs and evidence_snapshot or service_status.

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