apache_runtime_config

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

readOnlyHint=true already tells the agent this is a safe read, and the "[READ]" prefix merely restates it. The description says nothing about what the dump contains, whether it reflects live in-memory state versus on-disk files, how large the output could be, or whether a reload is needed to observe changes.

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 short sentence, front-loaded with the action and resource, with no filler. The "[READ]" prefix is wasted space since the annotation already declares read-only behavior, which is the only minor inefficiency.

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, the description is the only place to learn what a "parsed runtime configuration" dump looks like, and it does not say. Combined with an undocumented optional target parameter, an agent has enough to attempt a call but not enough to predict or interpret the result.

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 single parameter "target" has 0% schema description coverage, so the description carries the full burden and provides nothing about it. An agent cannot tell whether target scopes to a vhost, a server, or a config section, or what null (the default) means versus supplying a value.

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?

"Dump Apache's parsed runtime configuration" gives a specific verb (dump) and a specific resource (the runtime/parsed config), which distinguishes it reasonably well from siblings like apache_config_check, apache_static_directives, and apache_vhosts. It stops short of explicitly naming which sibling to prefer, but the resource is concrete enough for an agent to form a hypothesis.

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 statement of when to use this instead of apache_config_check, apache_config_includes, apache_static_directives, or apache_probe, all of which sound adjacent. The only usage signal is the bracketed "[READ]" tag, which is implied by the annotation rather than a selection rule.

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