restart_indi_server

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

No annotations provided; description only mentions restart and optional port. Missing details such as whether it stops running drivers, disconnects clients, or requires authentication. Minimal behavioral disclosure.

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?

Single sentence, front-loaded with action and resource, no extraneous words.

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?

Lacks details about restart behavior (stop then start), return values, and impact on connected components. With an output schema and sibling tools, more context is needed for full understanding.

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?

Single 'port' parameter with 0% schema description coverage. Description adds that it 'optionally switching to a new port', which provides some meaning beyond schema (integer/null), but doesn't specify default behavior (keep same port). Partially compensates.

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?

Clearly states the verb 'Restart' and the resource 'INDI server (indiserver)', and includes optional port switching. Distinguishes from siblings like start_indi_server, stop_indi_server.

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?

Indicates optional port change, but lacks explicit guidance on when to use vs alternatives like start or stop. Context is clear but no exclusions or when-not scenarios.

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