nginx_config

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

With no annotations, the description itself conveys that all actions are non-mutating inspections and identifies the underlying commands (nginx -t, nginx -T) and what each action returns. It does not mention permissions or potential command output size, but it makes operational behavior reasonably clear.

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 states the tool's purpose and then maps each action to a specific behavior. There is no filler or unnecessary repetition beyond what makes the description standalone and useful.

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 tool with four actions and one optional parameter, the description covers each action's behavior and implies what output the agent can expect. It could add permission requirements or error/exit-code behavior, but the core invocation requirements are complete.

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 coverage is 100%, so the schema already documents the action enums and the site parameter in full. The description restates action behavior but adds essentially no parameter detail beyond the schema, keeping it at the baseline.

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 specific action verbs (read, validate, inspect) tied to the nginx configuration resource and enumerates the four concrete actions. This clearly distinguishes it from sibling system/service inspection tools.

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 establishes clear context: this tool is for reading, validating, and inspecting nginx configuration, so an agent can recognize when it applies. It does not explicitly name alternatives or when-not-to-use conditions, but the sibling tools are generic system utilities with minimal overlap.

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