jev_locate

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

With no annotations, the description carries the burden of conveying the operation's behavior. 'Find' clearly signals a read-only lookup, and it names what is returned (source file and line). It does not explicitly mention error behavior when no match is found, but for a simple locate tool this is a reasonable level of disclosure.

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 a single sentence that front-loads the action and target, includes a helpful example, and contains no filler. Every word contributes to understanding.

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—one required parameter, no output schema, no annotations—the description covers the essential facts: what it locates, the input format, and the kind of result. It is sufficiently complete for an agent to invoke it correctly.

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 the description must compensate. It does by explaining that `code` is a 'Figma layer code' and providing a concrete format example (@a3.0.2.1). This adds meaning beyond the raw string type in the schema, though it could be more precise about allowed formats.

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 states a specific verb ('Find'), a precise resource ('source file and line'), and a clear input ('Figma layer code') with an illustrative example. This makes the tool's purpose unmistakable and distinguishes it from the sibling sync/execution tools.

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?

The description implies when to use the tool: when you have a Figma layer code and need its source location. However, it does not explicitly contrast this with sibling tools like jev_execute or jev_sync_now, nor does it state when not to use this tool.

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