capture_react_profile

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

The description only discloses 'writes artifact' as a side effect, with no mention of whether profiling is started/stopped, any state changes, or potential impact on the target. With no annotations, the description does not adequately convey behavioral traits such as whether the operation is read-only or has side effects beyond writing an artifact.

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 concise sentence with no wasted words, front-loading the primary action and then adding the method and outcome. It is efficiently structured and easy to read.

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 lacks essential context: it does not explain what 'capture' entails in relation to start/stop react profile, what the artifact is, how it is stored or accessed, or any interaction with sibling tools. No output schema exists, so the description alone is insufficient for an agent to understand the full behavior and outputs.

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%, and the description does not mention or explain the parameters targetId and profileMs at all. Since there are two parameters that likely carry important meaning, the description must compensate but fails to do so.

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 specific action ('Capture React Profiler session'), the method ('via Fusebox CDP'), and the outcome ('writes artifact'). This distinguishes it from sibling tools like start_react_profile, stop_react_profile, and capture_js_profile, which have different verbs or targets.

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?

No guidance is provided about when to use this tool versus alternatives. The description does not mention any prerequisites, exclusions, or relationships to the sibling tools, leaving the agent to infer usage context.

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