locate

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

The description goes beyond the simple read-only annotation by specifying that the location is 'stored encrypted on disk' and is 'relative to the vault's folder.' This crucial detail helps the agent understand the nature of the output path.

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 description is highly concise, immediately stating the primary function and followed by a single, relevant use case ('handy for sync conflicts or backups'). There is no wasted language.

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?

The tool is complete. It defines exactly what information the tool provides (the encrypted disk location) and why that information is valuable, allowing an agent to invoke it with the necessary context (vault name and file path).

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 100%, meaning the input schema adequately defines 'path' and 'vault'. The description provides a functional context but does not add specific semantic meaning beyond what the structured schema already covers, meeting the baseline requirement.

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 clearly states the tool's function: locating the encrypted on-disk storage path of a specific file or folder within an open vault. This specific function is highly distinct from sibling tools like 'read_file' or 'find', which retrieve data or metadata.

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?

It provides excellent context for when to use the tool by naming specific scenarios: 'handy for sync conflicts or backups.' While it doesn't explicitly exclude all other tools, the highly specialized nature of locating the encrypted storage location makes its usage guidelines clear.

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