Move Document (Outline)

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false. Description adds 'Requires write access' which aligns with mutation nature. No contradictions, but beyond that, no additional behavioral traits disclosed (e.g., side effects on permissions or URLs). Minimal added value over annotations.

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?

Extremely concise: two sentences that front-load the core purpose and a necessary prerequisite. Every word is relevant and no superfluous text.

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 simplicity (3 params, no output schema), the description should cover basic behavioral context such as what happens to the document's position, any side effects on URLs or permissions. The description is too brief and leaves important aspects unspecified.

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 0%, so description must compensate. It implicitly references collectionId and parentDocumentId but does not explain their semantics, format, or optionality. The required 'id' parameter is not described at all. Fails to add meaning beyond what the schema provides.

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?

Description clearly states the action (move) and resource (document), and specifies it can be to another collection and/or under another parent document. This distinguishes it from siblings like outline_archive_document, outline_delete_document, etc.

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?

Description mentions prerequisite 'Requires write access' but does not provide explicit guidance on when to use versus alternatives or when not to use. Context is implied but lacks exclusions.

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