ClawSouls MCP Server

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

Annotations indicate readOnlyHint=false, implying a write operation, which aligns with the description's 'Download' and 'generate' actions. The description adds context about downloading from ClawSouls and generating a file, but does not disclose behavioral traits like authentication needs, rate limits, or side effects beyond what annotations provide. No contradiction with annotations exists.

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 that front-loads the core action and outcome without unnecessary words. Every part of the sentence ('Download a persona from ClawSouls and generate a CLAUDE.md file') contributes directly to understanding the tool's purpose, making it highly concise and well-structured.

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's complexity (a write operation with 3 parameters) and the absence of an output schema, the description is minimally adequate. It covers the basic action but lacks details on the generated file's format, location, or any error conditions. With annotations providing some safety context, it meets a baseline level of completeness but leaves gaps for effective agent 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 description coverage is 100%, with clear descriptions for owner, name, and output_dir parameters. The description does not add meaning beyond the schema, such as explaining what a 'Soul owner' or 'Soul name' represents in ClawSouls context, but the high schema coverage justifies the baseline score of 3.

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 specific action ('Download a persona from ClawSouls') and the outcome ('generate a CLAUDE.md file'), using precise verbs and identifying the resource. It distinguishes itself from sibling tools like soul_get, soul_search, and soul_scan by focusing on installation and file generation rather than retrieval, searching, or scanning operations.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or comparisons to sibling tools such as soul_get (which might retrieve persona details) or soul_search (which might find personas), leaving the agent without context for tool selection.

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