Create a browser URL that preloads a public prompt or opens freeform generation.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "create_generation_url"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| locale | No | Optional locale code. | |
| promptSlug | No | Optional public prompt slug. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, and it does disclose that the output is a browser URL and that behavior differs between prompt-preload and freeform modes. It does not state whether the operation has side effects, whether it requires the prompt to be public/accessible, or how errors surface, leaving real behavioral gaps.
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?
A single compact sentence that front-loads the action and then the two supported modes. Every clause earns its place with no redundancy.
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 two-optional-parameter tool with full schema coverage and no output schema, the description is nearly sufficient: it explains the tool's purpose and both usage modes. Minor gaps remain around locale behavior and the exact semantics of omitting promptSlug.
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 description coverage is 100%, so both optional parameters are already documented in the schema. The description adds only loose mapping ('public prompt' to promptSlug) and says nothing about locale, so baseline 3 is appropriate.
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 states a specific verb and resource ('Create a browser URL') and clarifies the two outcomes the URL can produce: preloading a public prompt or opening freeform generation. It is clear on its own, though it does not explicitly distinguish itself from siblings like get_prompt or search_prompts.
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?
Usage is implied by the two modes described: provide a prompt to preload, or omit it for freeform generation. However, it never states when an agent should prefer this tool over get_prompt or search_prompts, nor any exclusions or prerequisites.
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.