MCP Cliniko Server

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

No annotations are provided, so the description carries full burden. It discloses the destructive action ('Delete') and target criteria, but lacks details on permissions needed, whether deletion is reversible, rate limits, or what happens on success/failure. For a destructive tool with zero annotation coverage, this is insufficient.

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 a single, efficient sentence with zero waste—it directly states the action, target, and criteria without unnecessary words. It is appropriately sized and front-loaded for quick understanding.

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?

Given the destructive nature and lack of annotations/output schema, the description is minimally adequate but incomplete. It specifies what gets deleted but omits critical behavioral context like safety warnings, confirmation steps, or response format. For a high-stakes deletion tool, more completeness is warranted.

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?

The tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately focuses on behavior rather than inputs, meeting the baseline for parameterless tools.

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 ('Delete') and target resource ('all test patients'), with precise criteria defining test patients (emails ending in @gmail.com, @outlook.com, etc.). It distinguishes from siblings like 'delete_patient' by specifying bulk deletion of test data only.

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 implies usage context for cleaning up test data, but does not explicitly state when to use this vs. alternatives like 'cleanup_comprehensive_test_data' or 'delete_patient'. It provides clear scope (test patients by email domain) but lacks explicit exclusions or prerequisites.

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