get_account_linksLinks to create an account, sign in and manage connections.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| mcp | Yes | ||
| links | Yes | ||
| disclosureUnits | Yes | ||
| mcpAvailability | Yes | Public availability follows release controls. | |
| availabilityMessage | Yes | ||
| browserConfirmationRequired | Yes |
Changes observed during successful MCP inspections.
Output schema / descriptionPrevious value: -"MCP get_account_links result: official links for account creation, sign-in, account management and comparing plans, with a pointer to kunkafa.com."New value: +"MCP get_account_links result: official links to create an account, sign in, manage connections and read the documentation, with a pointer to kunkafa.com."Output schema / properties / mcpAvailability / descriptionPrevious value: -"Public availability follows release controls. Plan MCP capabilities may be listed before public availability."New value: +"Public availability follows release controls."Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": false,
+ "description": "MCP get_account_links result: official links for account creation, sign-in, account management and comparing plans, with a pointer to kunkafa.com.",
+ "properties": {
+ "availabilityMessage": {
+ "type": "string"
+ },
+ "browserConfirmationRequired": {
+ "const": true
+ },
+ "disclosureUnits": {
+ "const": 0
+ },
+ "links": {
+ "additionalProperties": false,
+ "properties": {
+ "documentation": {
+ "pattern": "^https://kunkafa\\.com/",
+ "type": "string"
+ },
+ "manage": {
+ "pattern": "^https://kunkafa\\.com/",
+ "type": "string"
+ },
+ "signin": {
+ "pattern": "^https://kunkafa\\.com/",
+ "type": "string"
+ },
+ "signup": {
+ "pattern": "^https://kunkafa\\.com/",
+ "type": "string"
+ }
+ },
+ "required": [
+ "signup",
+ "signin",
+ "manage",
+ "documentation"
+ ],
+ "type": "object"
+ },
+ "mcp": {
+ "const": "https://kunkafa.com/mcp"
+ },
+ "mcpAvailability": {
+ "description": "Public availability follows release controls. Plan MCP capabilities may be listed before public availability.",
+ "enum": [
+ "coming_soon",
+ "available"
+ ]
+ }
+ },
+ "required": [
+ "mcp",
+ "links",
+ "browserConfirmationRequired",
+ "disclosureUnits",
+ "mcpAvailability",
+ "availabilityMessage"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, and the description adds nothing behavioral on top of that — no indication of what the returned links are for, whether they expire, or whether auth is required. The phrase 'create an account, sign in' could even be misread as a write operation, though it most plausibly describes the purpose of the returned links.
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 short sentence with no padding, but it is under-specified rather than genuinely concise — the sentence is ambiguous about what is returned and does not front-load a clear action verb.
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 not be described, and there are no parameters to document. However, for a discovery tool the description still leaves the core question — what these links are and when an agent should fetch them — unresolved.
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 takes zero parameters, so the schema carries the full contract and the description has nothing to compensate for. Baseline 4 applies for a no-parameter tool.
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 name and description both center on 'links', but the description is a bare noun phrase with no verb and ambiguous grammar: it is unclear whether the tool returns URLs for account creation/sign-in/connection management or performs those actions itself. It conveys the resource loosely but does not clearly distinguish it from siblings like get_usage or get_performance.
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?
No when-to-use guidance, no prerequisites, and no mention of any alternative tool. The agent is left to infer that this is a discovery/helper call with no stated trigger condition.
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.