panelica_server_post_v1_server_services_name_stop

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

Without annotations, the description adds a cautionary note about the potentially dangerous nature of stopping a service, which provides behavioral context beyond the schema.

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 concise with two sentences and supplementary HTTP info, front-loading the action and caution.

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's simplicity (single param, no output schema), the description covers the essential action and caution; however, missing details like post-stop state or how to restart.

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?

With 100% schema coverage, the description does not add meaning beyond the schema; the param name is already described as 'Path parameter: name'.

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 it 'Stops a specific service' using a strong verb and specific resource, distinguishing it from sibling tools like start and restart.

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 warns 'Use with caution' but does not specify when or when not to use it, nor does it mention alternatives like start or restart.

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