apache_error_log

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

Annotations already declare readOnlyHint=true, and the "[READ]" prefix merely restates that. The description does add genuine context beyond annotations: the log path is operator-configured (so no arbitrary path access) and output is explicitly truncated. It does not say how truncation is signaled or what a tail of an empty/rotated log looks like.

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?

A single front-loaded sentence with no filler; the read-only marker and the two key traits (operator-configured path, truncation) come first. It is efficient, though the terseness trades away information the parameters need.

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 two-parameter tool with no output schema and 0% schema coverage, the description should explain what `target` and `limit` do and what the returned entries look like. Neither is covered, leaving the agent guessing on invocation despite the clean one-line framing.

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% for two parameters. "Explicit truncation" loosely gestures at `limit` (default 50) but never states that it caps lines returned, and `target` is left completely unexplained — an agent cannot tell whether it selects a log path, a host, or a vhost.

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?

Specific verb ("Tail") plus specific resource ("Apache error log") tells an agent exactly what the tool returns. It is distinguishable from the access-log-flavored sibling apache_access_status, though it never names that sibling explicitly and the ambiguous "target" parameter leaves the log source slightly open.

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?

There is no when-to-use statement, no exclusion, and no pointer to alternatives such as apache_access_status or apache_diagnose when the error log is not the right place to look. The agent must infer usage purely from the tool name and the word "Tail".

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