get_record_by_identifier

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

No annotations provided, so description carries full burden. It successfully explains lookup scope (UUID works across all open databases), but misses return value specification, error handling (what if ID not found?), and read-only safety confirmation.

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?

Two well-structured sentences with zero waste. First sentence establishes core purpose; second provides critical parameter logic. Appropriately front-loaded.

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 100% schema coverage, parameters are well-documented. However, with no output schema and multiple sibling 'get_record_*' tools, the description should specify what this returns (likely a record reference/metadata) to distinguish from content/properties retrieval.

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?

With 100% schema coverage, baseline is 3. The description adds valuable semantic context about the relationship between parameters—specifically the cross-database vs single-database scope constraints that affect which identifier to use.

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?

Clear verb ('Get') and resource ('DEVONthink record') with specific identifier types (UUID/ID). However, it doesn't distinguish from sibling 'lookup_record' or clarify what 'get' returns (metadata vs reference) compared to 'get_record_content' or 'get_record_properties'.

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?

Provides clear guidance on parameter selection (UUID preferred for cross-database, ID requires databaseName), but lacks explicit 'when to use vs alternatives' guidance regarding 'search', 'lookup_record', or other retrieval tools.

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