capture_js_profile

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

The description discloses a concrete side effect (writes artifact under .dejank/artifacts), which adds value beyond the schema. However, it does not state whether the operation is read-only, how it interacts with an ongoing JS profiling session, or what the return value is. No annotations are present, so the description carries the full burden but only partially fulfills it.

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?

A single concise sentence that front-loads the core action and includes key details about duration and artifact location. No wasted words, perfectly sized for a quick 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?

The description covers the main purpose and artifact destination, but omits details about the targetId parameter, the return format, and how it relates to sibling profiling tools (e.g., whether it conflicts with start_js_profile). Given the tool's simplicity, it is not severely incomplete but leaves room for improvement.

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?

The description explicitly mentions 'durationMs' and its role, which is helpful given 0% schema coverage. However, 'targetId' is not explained at all, leaving a gap for one of the two parameters.

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 action ('Capture'), the resource ('Hermes JS CPU profile'), and includes the duration parameter. It distinguishes itself from sibling tools by specifying 'Hermes JS' (vs React) and using 'capture' (vs start/stop).

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 usage is implied: provide a duration to capture a profile. However, there is no explicit mention of when to use this tool over start_js_profile/stop_js_profile or other alternatives, nor any exclusions.

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