wikijs_cross_repo_link

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. The word 'Create' signals a write operation and suggests a persistent mapping, but the description gives no information about idempotency, duplicate handling, whether existing mappings are overwritten, or what valid relationship values are beyond the schema's loose examples.

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, front-loaded sentence with no unnecessary filler. It is concise and readable, though the brevity comes at the cost of behavioral and usage context.

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?

With no annotations, no output schema, and six required parameters, the description alone is insufficiently complete. It does not explain what the mapping means structurally, what happens when the tool runs, or how the result is represented, and it provides no usage context to guide correct invocation beyond the schema.

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%, so the structured definitions already document all six parameters clearly. The description adds no additional meaning beyond the high-level idea of a mapping, so it does not go beyond the baseline expected when the schema is complete.

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 a specific verb and resource: 'Create architectural mapping between repositories.' It is reasonably distinct from sibling page- and repository-creation tools because it emphasizes relationships between repositories. It is slightly underspecified because 'architectural mapping' is not elaborated, but the schema fills in the main entities.

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?

There is no guidance on when to use this tool versus alternatives such as wikijs_create_repo_structure or wikijs_create_page. The phrase 'between repositories' implies a cross-repository scenario, but the description does not state prerequisites, exclusions, or when another tool would be more appropriate.

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