apache_config_check

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

The readOnlyHint annotation already establishes that this is purely a read operation, and the description is consistent with that. What it adds beyond the annotations is only the phrase 'native config syntax test'; it says nothing about what happens on failure (exit status, error output, line numbers) or whether it validates the live server config versus a supplied target.

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?

It's a single sentence with no redundant wording and the key concept is front-loaded. The brevity is appropriate in form, though it edges into under-specification rather than tightness.

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 no output schema and 0% parameter coverage, the description must explain both the ambiguous 'target' argument and what a syntax-test result looks like. It does neither, so an agent cannot confidently determine valid input values or interpret the outcome.

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 the single, nullable 'target' parameter, so the description carries the full burden and fails it. The description never mentions 'target' and does not explain what a target means here (a config file path, a vhost, a server instance), which is the one piece of information an agent needs to call this correctly.

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 states a specific verb and resource: run Apache's native config syntax test. That is concrete enough to separate it from siblings like apache_config_includes or apache_runtime_config, although it doesn't name those siblings or contrast itself with apache_diagnose explicitly.

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 guidance at all: nothing says to run this before apache_graceful_reload, nothing says when apache_diagnose would be preferable, and nothing states prerequisites. The only implicit cue is the [READ] tag, which merely restates the readOnlyHint annotation.

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