diagnose_hydration_and_suspense

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

No annotations are provided, so the description carries full burden. It discloses that the tool analyzes mount durations, unmount events, and timelines, suggesting a read-only diagnostic behavior. However, it does not explicitly state whether the tool modifies the profile file, requires write permissions, or has any side effects. The methodology hint is useful but incomplete.

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, efficient sentence that front-loads the main purpose and then provides the analytical approach. There is no redundancy or filler, every word contributes to understanding the tool's function.

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?

For a diagnostic tool with two well-documented parameters and no output schema, the description covers the core purpose and methodology adequately. The only minor gap is the lack of detail about return format, but given the tool's narrow scope and schema richness, it is sufficiently complete.

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 100%, with both profile_path and waterfall_threshold_ms clearly described in the input schema. The description adds no extra parameter information, but the schema already provides sufficient semantics, so a baseline score of 3 is appropriate.

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 uses a specific verb 'Detects' and names two distinct targets: server-client hydration mismatches and sequential nested Suspense waterfalls. It also mentions the analysis method (mount durations, unmount events, timelines), which clearly differentiates it from sibling tools like find_spurious_renders or get_render_summary.

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 when to use the tool (when hydration or Suspense waterfall issues are suspected), but it does not explicitly compare with alternatives or state when not to use it. It doesn't mention exclusions or prerequisites, so guidance is present but not strongly articulated.

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