start_react_profile

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only mentions that it should be paired with a stop tool, but does not disclose what starting the profiler does to the app (e.g., performance impact), whether it requires a target, or any side effects. This is insufficient for a profiling tool.

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, front-loaded with the action, and has no wasted words. It is concise and efficient, though it may be too brief for the tool's complexity. Still, the conciseness dimension rewards brevity and structure, which is well-executed.

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 moderate complexity (one optional parameter, no output schema, no annotations), the description is incomplete. It does not explain what the profiler does, how to use the targetId, or how this tool relates to siblings like 'start_js_profile' and 'capture_react_profile'. The pairing hint is the only contextual detail provided.

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 schema has one parameter 'targetId' with 0% schema description coverage, and the description does not mention or explain this parameter at all. Since the description fails to compensate for the low coverage, parameter semantics are severely lacking.

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 ('Start') and the resource ('React Profiler (Fusebox)'). It is specific about what it starts, but it does not explicitly distinguish from sibling tools like 'start_js_profile' or 'capture_react_profile', which would be needed for a perfect score.

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 instruction to 'pair with stop_react_profile' implies a profiling session lifecycle, giving some usage context. However, it lacks any guidance on when to choose this tool over alternatives like 'start_js_profile' or 'capture_react_profile', and no exclusions are mentioned.

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