nocobase-mcp-server

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

No annotations are provided, so the description carries the full burden. It discloses key behavioral traits: it performs a 'deep copy' (not shallow), attaches the copy to the same parent automatically, and returns the new block's data. However, it lacks details on permissions, error handling, or side effects, which are important for a mutation tool.

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 ('duplicate') and includes all essential details (deep copy, attachment, return value). There is no wasted wording, 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 no annotations and no output schema, the description is moderately complete. It covers the tool's purpose and basic behavior but lacks details on return format, error conditions, or authentication needs. For a mutation tool with no structured support, more context would be beneficial.

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 100% description coverage, with the single parameter 'uid' documented as 'Flow model UID to duplicate'. The description adds no additional parameter semantics beyond this, but since there is only one parameter and the schema is fully covered, the baseline is high. No compensation is needed.

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 ('duplicate'), the resource ('existing flowPage block/model'), and the scope ('deep copy' and 'attach it to the same parent'). It distinguishes from siblings like 'create_page' (new creation) and 'destroy_flow_model' (deletion) by focusing on replication of an existing model.

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 implies usage when needing to copy a flow model, but does not explicitly state when to use this tool versus alternatives like 'create_page' (for new models) or 'move_flow_model' (for relocation). No exclusions or prerequisites are mentioned, leaving some ambiguity about context.

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