stop_studyStop panel recruitment, close the target cycle, and settle/release the active reward hold. Call only after the human explicitly chooses to end this study's fieldwork.
| Name | Required | Description | Default |
|---|---|---|---|
| study_id | Yes | ||
| organization_id | No | Organization for this operation and billing. Use list_organizations to choose an active membership. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes | The stopped study. |
Changes observed during successful MCP inspections.
Input schema / properties / organization_id / descriptionPrevious value: -"Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet."New value: +"Organization for this operation and billing. Use list_organizations to choose an active membership."Input schema / properties / organization_idAdded value: +{
+ "description": "Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet.",
+ "maxLength": 128,
+ "minLength": 1,
+ "type": "string"
+}Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / additionalPropertiesRemoved value: -falseInput schema / properties / study_id / patternAdded value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Output schema / properties / result / additionalPropertiesPrevious value: -trueNew value: +{}Output schema / properties / result / properties / dashboard_url / $refRemoved value: -"#/properties/result/properties/name"Output schema / properties / result / properties / dashboard_url / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / result / properties / study_link / $refRemoved value: -"#/properties/result/properties/name"Output schema / properties / result / properties / study_link / typeAdded value: +[
+ "string",
+ "null"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered; the description's added value is spelling out what actually happens (recruitment halted, cycle closed, reward hold settled/released), which is real consequence-level detail. It still does not state whether the operation is reversible or whether already-collected data is retained.
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 sentences, no waste; the effect list leads and the invocation gate follows. Every clause earns its place.
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?
An output schema exists, so return values need no explanation, and annotations cover the safety profile. For a terminal, destructive lifecycle operation the description is nearly complete, with only reversibility and the pause-vs-stop boundary left unstated.
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 50% and the description adds nothing about either parameter. study_id is self-explanatory by name and format, and organization_id is documented in the schema with a pointer to list_organizations, so the schema carries the load and baseline 3 applies.
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?
Uses a specific verb and enumerates the concrete effects: stopping panel recruitment, closing the target cycle, and settling/releasing the reward hold. An agent immediately knows what the tool does, but the description never names pause_study or delete_study, so the distinction from those near-neighbors must be inferred from the 'end this study's fieldwork' phrasing.
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?
'Call only after the human explicitly chooses to end this study's fieldwork' is a clear, hard precondition that rules out speculative or automated invocation. It stops short of explicitly routing the agent to pause_study for temporary halts or delete_study for removal, which would have earned a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.