stop_react_profile

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

With no annotations, the description carries the full burden. It discloses the core actions (stop and save) but says nothing about prerequisites (e.g., an active profiling session), side effects, error behavior, or what happens to the artifact. This is a significant gap for a mutating 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, concise sentence (8 words) that is front-loaded with the primary action. Every word earns its place, with no redundancy or filler.

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 tool is simple (0 parameters, no output schema), and the description covers the essential behavior. It is reasonably complete, though it could benefit from noting the expected lifecycle (e.g., must be called after start_react_profile) and what happens if no session is active. These gaps are minor given the low complexity.

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 tool has zero parameters, and the schema coverage is 100% (trivially). The description adds no parameter-specific meaning, but none is needed. Per calibration guidance, 0 params yields a baseline of 4.

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 a specific verb ('Stop') and resource ('React Profiler'), plus an additional action ('save profilingData artifact'). It effectively distinguishes itself from siblings like stop_js_profile and start_react_profile by naming the profiler type and the artifact output.

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 usage after starting the React Profiler but provides no explicit when-to-use or when-not-to-use guidance, nor any mention of alternatives. It is minimally viable but lacks the explicit context that would make it a stronger 4 or 5.

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