Nginx Config

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool performs a check but does not describe what happens on success/failure, whether it modifies state, or the output format. This is a significant gap for a tool that could return validation errors or require specific access.

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?

The description is a single short phrase, which is efficient but under-specifies the tool. It lacks the necessary detail to be genuinely helpful, so it is not true conciseness but rather under-specification.

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?

Even though an output schema exists, the description provides no context about the check's scope, expected inputs, or return values. With no annotations and a free-form parameter, the tool is incomplete for an agent to use correctly.

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 input schema defines a single 'params' field that is either null or an arbitrary object with additionalProperties true, and schema description coverage is 0%. The description adds no explanation of what parameters should be passed, making the tool effectively undocumented for parameter use.

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 'Проверка конфигурации Nginx' (Check Nginx configuration) provides a specific verb and resource, clearly distinguishing it from siblings like nginx_status or nginx_logs. However, it does not specify the nature of the check (e.g., syntax validation, reload test), which slightly limits clarity.

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 guidance is given on when to use this tool versus alternatives such as nginx_status or nginx_upstream. The description does not mention any conditions, prerequisites, or exclusions, leaving the agent without routing information.

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