find_hydration_errors

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that the tool detects hydration mismatches but does not reveal whether it is read-only, how it performs the detection, what it returns, or how it behaves when no mismatches exist. This is a significant gap for a diagnostic 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 two short sentences with no extraneous information. It front-loads the primary action and adds a relevant usage context. Every word earns its place.

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 lack of an output schema and annotations, the description is insufficiently complete. It does not explain the return value, the nature of the output (e.g., list of errors, boolean), or any prerequisites. For a debugging tool, this leaves key operational details undisclosed.

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, so schema coverage is trivially complete. The description adds no parameter information, but with no parameters, that is unnecessary. Per the baseline for 0 params, a score of 4 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 states 'Detect SSR hydration mismatches' with a specific verb and resource. It is distinct from sibling tools by its unique focus, though it does not explicitly name alternatives. The addition of 'Essential for Next.js/Remix debugging' gives context but does not fully disambiguate from all related debugging tools.

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 phrase 'Essential for Next.js/Remix debugging' implies a use case but does not provide explicit guidance on when to use this tool versus alternatives, nor does it state when not to use it. There is no mention of prerequisites or exclusions, leaving the usage context somewhat vague.

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