react-profiler-status

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

With no annotations, the description fully discloses side-effect-free nature, server-side ownership verification, absence of token-threading, return fields, and the taken_over behavior after process restart. This is comprehensive for a status check 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?

Relatively concise with no redundant information, but slightly dense. Each sentence adds meaningful context. Could be more structured (e.g., bullet points) but still effective.

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 no output schema, the description adequately explains return shape and important states (taken_over). Also clarifies ownership verification and token handling. Fully addresses likely agent questions.

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%, so baseline is 3. The description adds value by linking device_id to debugger-connect and noting port's default, but does not elaborate further. Slight improvement over baseline.

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?

Clearly states the verb 'Check' and resource 'state of the React profiler session', with the critical qualifier 'without side effects'. Distinguishes from sibling tools like react-profiler-start/stop by focusing on status inspection.

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 specifies when to use (after interruption) and provides decision guidance: continue with stop, start new session, or reconnect. Even gives a concrete alternative command (react-profiler-start { force: true }) for the taken_over case.

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