project_transfer

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

Annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false) cover the safety profile, and the description adds substantial context: originals remain local, destination must be fresh, processing must be halted, and approval is mandatory. It does not disclose failure/atomicity or idempotency behavior around operationId, which would complete the picture.

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 critical precondition is front-loaded ('ONLY after explicit researcher approval'), and every sentence carries operational weight. A couple of clauses are densely packed and run together, but there is no filler.

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 complex, no-output-schema, 0%-coverage mutation tool this covers the prerequisite and safety story well. It still omits semantics for several required parameters (operationId, expectedRevision) and any note on outcome or failure handling, so an agent can trigger it but cannot fully reason about the call contract.

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% across 7 parameters, so the description must carry the burden. It clarifies dispatchersStopped (stop processing in both clients before attesting) and implies reviewer/approvalText via the approval requirement, but leaves projectId, targetProjectId, operationId, and expectedRevision (likely a concurrency token) entirely unexplained.

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?

States a specific verb and resource (transfer a local case) plus the destination (configured Astra database) and scope (preserving history and budget, originals stay local). It is clear, but it does not explicitly differentiate itself from sibling tools like project_copy, project_restore, or transfer_recover, leaving the agent to infer which transfer variant applies.

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?

Gives strong preconditions: only after explicit researcher approval, stop page processing in both clients before attesting dispatchersStopped, and the destination must be fresh. However, it never names the sister tools that handle the recovery/status follow-ups (transfer_recover, transfer_status), so the agent gets 'when' but not the surrounding alternatives.

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