rpg-mcp

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions that workflows 'automate multi-step operations,' which implies mutation or creation actions, but fails to disclose critical behavioral traits such as permissions required, whether execution is idempotent, error handling, or what happens on failure. For a tool with zero annotation coverage and no output schema, this leaves significant gaps in understanding its behavior.

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 appropriately front-loaded with a clear purpose statement, but it includes lengthy JSON examples that, while helpful, could be considered excessive for a concise description. The examples earn their place by clarifying usage, but the overall structure is somewhat bloated, reducing efficiency compared to a more streamlined approach.

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 complexity of executing workflows (a multi-step automation tool) with no annotations and no output schema, the description is moderately complete. It explains the purpose and provides usage examples, but it lacks details on behavioral aspects like error handling, permissions, or return values. This leaves gaps that could hinder an AI agent's ability to use the tool effectively in all contexts.

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 input schema has 0 parameters with 100% coverage, so the schema itself provides no parameter information. The description compensates by including two detailed JSON examples that illustrate the expected input structure (e.g., using 'template' and 'params' or 'workflow' with nested steps). This adds substantial semantic value beyond the empty schema, effectively documenting the parameters through examples, though it lacks formal definitions.

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 tool's purpose: 'Execute a workflow from a template or inline definition.' It specifies the verb ('execute') and resource ('workflow'), and distinguishes it from siblings by focusing on multi-step automation rather than single operations. However, it doesn't explicitly differentiate from all siblings (e.g., 'batch_create_characters' is also multi-step), so it's not a perfect 5.

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 provides implied usage guidelines by giving examples of when to use the tool (e.g., 'automate multi-step operations like creating a full party, setting up an encounter, or populating a village') and includes concrete examples for templates and inline workflows. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., when to use 'execute_workflow' vs. calling individual tools like 'create_party' directly), so it doesn't reach the clarity of a 4 or 5.

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