disable_engine

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

With no annotations, the description must disclose side effects, but it only says 'Disable... in settings.yml'. It does not mention whether the change is persistent, reversible, requires a restart (e.g., via restart_searxng_container), or what happens if the engine name is invalid. This is insufficient for a mutation tool.

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 sentence plus an Args list with no filler or repetition of schema fields. Each element contributes to clarifying the operation, making it appropriately sized and front-loaded.

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?

Despite having an output schema, the description is minimal for a config-modifying tool. It fails to explain whether SearXNG needs a restart, if the engine must exist, or how the result is returned. With no annotations and no post-steps, the description is incomplete for safe agent use.

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 properties have no descriptions (0% coverage), so the description compensates by defining engine_name with an example ('duckduckgo') and explaining settings_path as 'Optional path to settings.yml'. This adds meaning beyond the bare schema, though it could be more explicit about defaults and validation.

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 clearly states 'Disable a specific search engine in SearXNG settings.yml'—a specific verb (disable) and resource (search engine in a config file). This distinguishes it from sibling tools like enable_engine and set_engine_status.

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 provided on when to use this tool over alternatives. The description does not reference sibling tools, prerequisites, or post-conditions. It merely states the action and parameters, leaving the agent without context for selection.

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