Execute a Nakama API action

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

Describes automatic auth handling, noting different credential sources for console vs. client vs. authenticate endpoints. Mentions pagination behavior via auto_paginate and max_pages. No contradiction with annotations (destructiveHint=true, readOnlyHint=false).

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?

Three concise sentences: purpose, auth handling, and sibling distinction. No filler, but might benefit from bullet points for clarity. Still, efficient and front-loaded.

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?

Covers purpose, parameters, auth, pagination, and alternative tools. Lacks explanation of return values or error handling, but output schema is absent and the tool is well-described for its intended use.

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 provides 100% coverage with descriptions. The description repeats 'Provide path_params, query_params, and/or body as needed' but adds little beyond schema. 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?

Clearly states 'Execute any Nakama operation by its action_id' with specific verb and resource. References nakama_search_actions as the source of action_id. Distinguishes from sibling tool nakama_call_rpc.

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?

Explicitly advises when to use this tool vs. alternatives: 'For calling server RPCs prefer nakama_call_rpc (it encodes the payload correctly).' Also explains auth context for different action types (console, client, authenticate).

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