move_record

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

With no annotations provided, the description carries the full burden. It successfully discloses the return value ('updated record properties'), but omits other behavioral details like error conditions, cross-database limitations, or explicit confirmation that the record is removed from the source location.

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?

Four well-structured sentences with zero waste: purpose first, resolution logic second, destination specification third, and return value fourth. Every clause earns its place.

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 6 parameters, no annotations, and no output schema, the description adequately covers the resolution logic, destination requirements, and return format. Minor gaps remain regarding error handling and side effect specifics.

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?

Despite 100% schema coverage, the description adds valuable semantic context by establishing a preference hierarchy (uuid is 'preferred') and consolidating the parameter relationships into a coherent resolution strategy that aids agent reasoning.

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 opens with a clear, specific action ('Move a record') and context ('to a different group in DEVONthink'), distinguishing it from sibling tools like duplicate_record, replicate_record, or create_record.

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?

While the description excellently explains how to resolve source records (uuid preferred vs. other methods), it lacks explicit guidance on when to choose this over similar operations like replicate_record or duplicate_record, or prerequisites for the move operation.

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