brainforge-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 states the tool parses wiki markdown and rebuilds a graph, but it does not disclose critical traits such as whether this is a read-only or destructive operation, what permissions are required, how long it takes, or any rate limits. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence in Korean that directly states the tool's action. It is front-loaded with the core purpose and has no wasted words, making it highly concise and well-structured for its purpose.

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 tool has 0 parameters, 100% schema coverage, and an output schema exists, the description is minimally complete. However, it lacks details on behavioral aspects (e.g., whether it's destructive or read-only) and usage context, which are important for a tool that rebuilds a graph. The output schema may cover return values, but the description should still provide more context about the operation's nature and when to use it.

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, meaning no parameters are documented in the schema. The description does not add parameter details, which is appropriate since there are none. The baseline for 0 parameters is 4, as the description does not need to compensate for missing parameter information.

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 the tool's purpose: parsing wiki markdown to rebuild a graph. This is clear but vague about what 'rebuild' entails and doesn't distinguish it from sibling tools like 'graph_summary' or 'explain_node', which might also involve graph operations. It specifies the resource (wiki markdown) and action (parse and rebuild graph) but lacks specificity about the scope or outcome.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention any context, prerequisites, or exclusions, and it fails to differentiate from sibling tools such as 'graph_summary' (which might summarize a graph) or 'find_path' (which might navigate a graph). This leaves the agent without clear usage instructions.

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