execute_svc_command

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

With no annotations provided, the description must disclose behavioral traits such as destructive potential, authentication requirements, output format, and error behavior. It only says 'execute any SVC CLI command', which implies high risk but does not warn about possible destructive actions (e.g., 'rmvolume', 'rmhost') or output variability. This is a critical gap for a generic execution 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 very short (two sentences) and front-loaded. It wastes no words, though one sentence could be removed by merging the two.

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?

Given the tool executes arbitrary CLI commands with no output schema and no behavioral transparency, the description is insufficient. It should cover safety warnings, expected output, required permissions, and when to prefer the sibling tool. The current text does not meet the needs of an agent deciding whether to invoke this tool.

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 100%, so the parameter is fully documented in the schema. The description only adds the phrase 'any SVC command' which is already conveyed by the schema's dynamic example. Baseline 3 is appropriate.

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 the tool executes SVC CLI commands and highlights its generic nature. It differentiates from check_system_status by being a catch-all execution tool.

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 provides no guidance on when to use this tool versus check_system_status, nor does it mention any prerequisites, limitations, or when alternatives should be preferred. The agent is left without usage boundaries.

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