stop_wiki_server

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

Discloses graceful termination and fallback behavior. Annotations already provide readOnlyHint=false and destructiveHint=false; description adds nuance. No contradiction found.

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?

Two concise sentences, front-loaded with main action. Minor redundancy between first sentence and 'gracefully terminates', but overall efficient.

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?

No output schema; description does not specify return value on success, only fallback case. Open-world hint and other context partially compensate, but missing return info is a gap.

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 covers all parameters (100%), description references 'port' but adds no additional semantics beyond schema defaults and constraints.

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 tool stops a wiki server with graceful termination, distinguishing it from sibling tools like serve_wiki. The verb 'stop' and resource 'wiki web server' are specific.

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?

Provides fallback behavior if server not found, mentions no prior indexing needed. However, lacks explicit when-to-use vs alternatives, though context with sibling tools implies stopping vs starting.

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