akb_move

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

Despite no annotations, the description discloses key side effects: identity and git history are kept, old URI keeps resolving via redirect, graph links/publications are rewritten, and title is unchanged. This is substantial behavioral transparency, though it does not mention permission requirements or error conditions.

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?

Three sentences, front-loaded with purpose, then side effects, then usage constraint and alternative. No redundancy; every sentence provides distinct value.

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?

For a mutable operation with no annotations and no output schema, the description explains what changes, what remains, and side effects like redirects and link rewrites. It does not mention what happens if both collection and slug are unchanged (likely an error), but the constraint implies it. Overall fairly complete.

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 coverage is 100%, so baseline is 3. The description adds meaningful constraint: at least one of collection or slug must change, which is not evident from the schema alone. It also clarifies that title is not a parameter, reinforcing the distinction from akb_update.

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 moves or renames a document, changing its collection and/or slug while preserving identity and git history. This clearly distinguishes it from siblings like akb_update (title change) and akb_edit (content edit).

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?

Explicitly states when to use: to move/rename a document. Also gives an alternative: use akb_update to change the displayed title. The constraint that at least one of collection or slug must change provides clear usage guidance.

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