Shutdown Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly warns about the destructive consequence ('WARNING: This will stop all interception'), which is crucial behavioral information. However, it doesn't mention whether the shutdown is reversible, what happens to pending requests, or if there are any authentication requirements.

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 perfectly concise with two sentences that each earn their place: the first states the core action, the second provides critical warning information. It's front-loaded with the main purpose and wastes no 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?

For a destructive tool with no annotations and no output schema, the description provides good coverage of the core behavior and warning. However, it doesn't explain what happens after shutdown (e.g., server restart process, state persistence) or potential side effects beyond stopping interception, which would be helpful given the tool's critical nature.

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 parameters and 100% schema description coverage, the baseline would be 4. The description appropriately doesn't discuss parameters since none exist, and the schema already fully documents the empty input structure.

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 specific action ('Shutdown') and resource ('HTTP Toolkit server'), distinguishing it from all sibling tools which focus on interception, configuration, or monitoring rather than server lifecycle management. It provides a complete verb+resource+scope statement that is unambiguous.

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 clear context about when to use this tool by stating it 'will stop all interception,' implying it should be used when interception needs to be completely terminated. However, it doesn't explicitly mention when NOT to use it or name specific alternatives for partial shutdown scenarios.

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