create_system

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

The description discloses the concrete operations (shutdown or restart) and the endpoint, which adds useful behavior context. Annotations already indicate idempotent and non-destructive, and the description does not contradict them, though it does not explain side effects beyond the action names.

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 short and front-loaded, delivering the core purpose in the first sentence followed by the endpoint and parameter detail. Every sentence contributes meaningfully with no redundancy.

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 simple one-parameter tool with an output schema and clear annotations, the description provides enough context to invoke it correctly. It lacks fuller when-to-use or effect detail, but the low complexity and existing annotations cover most needs.

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 0% schema description coverageched, the description compensates by defining the `action` parameter and enumerating its allowed values: 'shutdown' and 'restart'. This is essential semantic information that the schema alone lacks.

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 explicitly states 'Shutdown or restart Bazarr', giving a specific action and resource. It also lists the two possible action values, making the tool's purpose unambiguous and distinct from siblings like create_system_backups or create_system_account.

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 makes clear that the tool is for shutdown/restart actions, so the primary usage intent is evident. However, it does not explicitly discuss when to prefer this over alternatives or mention any conditions/exclusions, leaving that to the agent's inference.

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