start_server

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

With no annotations, description reveals fail condition and error action value ('rejected_occupied'), adding context beyond schema. Lacks detail on success behavior or side effects.

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?

Three sentences, each serving a distinct purpose: action, fail case with alternative, and parameter requirements. No redundant text.

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?

Covers fail condition, required params, port specification rule, and relationship to sibling tool. No output schema needed; description is sufficient for a start operation.

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 coverage is 100%, baseline 3. Description adds that both parameters are required (already in schema) and that model_name must match a model from list_models, providing extra constraint.

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?

Description clearly states the action ('Start a model on an empty port'), verb 'start', resource 'model', and distinguishes from sibling 'swap_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?

Explicitly states when to avoid this tool (if a different model is running on the port) and directs to 'swap_server'. Also notes required parameters and that model_name must match 'list_models'.

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