react-profiler-start

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

Since no annotations exist, description carries full burden. It discloses delegation to in-app backend, returns already_running payload without clobbering, force reclaim behavior, and failure conditions (Hermes unreachable, Metro connection fail). However, does not mention potential performance impact or state modifications beyond profiling.

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?

Each sentence earns its place: main action, delegation, special case, usage guidance, return values, failure conditions. Well-structured with logical flow. Slightly longer than minimal but no dead content. Could be condensed slightly but remains efficient.

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 4 parameters, no output schema, and moderate complexity, the description covers purpose, usage workflow, behavioral edge cases, failure modes, and integration with sibling tools. It fully addresses the information gap needed for an AI agent to use the tool correctly.

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 100% (all 4 parameters described in schema). The description adds context for the force parameter (user approval before overtaking), which goes beyond the schema description. For other parameters, schema suffices, so description adds moderate extra semantic value.

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 starts with 'Start CPU profiling + React commit capture on the connected Hermes runtime,' which clearly states the verb (start) and resource (profiling on Hermes runtime). It distinguishes from siblings like native-profiler-start and react-profiler-stop by mentioning delegation to React DevTools backend and the parallel native profiling recommendation.

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?

Provides explicit guidance: ask user about native profiling before calling, recommend running both in parallel, ask user to perform interaction after starting, then call react-profiler-stop. Also explains when to use force=true and warns to get user approval before overtaking another session. No alternative guidance is missing.

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