manage_mock_server

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

Describes lifecycle actions but lacks disclosure of side effects, permissions required, or error behaviors. With no annotations, the description carries full burden and provides only basic operational details.

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 efficient sentences covering purpose and scope with no unnecessary 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?

Adequate for basic understanding but missing output expectations and error handling details. With no output schema, description should explain return values or success/failure signals.

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 with descriptions, but the description adds value by clarifying conditional requirements (e.g., openApiSpec and port needed for start command) beyond what the schema states.

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 it manages Specmatic mock servers with specific actions (start, stop, list) for frontend development. Distinguishes from sibling tools (run_contract_test, run_resiliency_test) which are different purposes.

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?

Implies usage for frontend development but does not explicitly state when to use this tool vs siblings or when not to use. No exclusion criteria or alternative suggestions.

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