start_js_profile

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

With no annotations, the description carries full burden. It only says 'Start', disclosing no side effects, whether targetId is required, how long profiling runs, or what happens after stopping. Minimal behavioral insight beyond the name.

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?

Single sentence, front-loaded with the primary action. The pairing hint adds useful context without bloat. Slightly terse but appropriately concise for a simple start command.

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 one undocumented parameter and no output schema, the description should compensate, but it omits targetId semantics and does not explain how results are obtained via stop_js_profile. Incomplete for effective invocation.

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 coverage is 0% and the description never mentions targetId. The agent receives no guidance on what targetId refers to or how to populate it, making the sole parameter semantically opaque.

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 and resource: 'Start Hermes JS CPU profiler'. It distinguishes from siblings by specifying 'Hermes JS' and by pairing with stop_js_profile, differentiating it from capture_js_profile or start_react_profile.

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?

Explicitly instructs to 'pair with stop_js_profile around a repro', giving clear usage context. It does not mention when not to use it or alternative tools like capture_js_profile, but the pairing note is valuable.

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