capture_errors

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

No annotations provided. Describes itself as free but lacks disclosure of side effects, authorization needs, or whether it modifies page state. The tool likely only reads errors, but this is not stated explicitly.

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?

Two sentences plus a free note, front-loaded with purpose. No redundant information.

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?

Adequately explains what the tool does and returns for a single-parameter tool without output schema. Missing details like timeout or error handling for inaccessible URLs, but overall complete enough.

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% with a clear description for the url parameter. The description adds context about capturing errors during page load and the return format, but does not provide substantial additional meaning beyond the schema.

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 it captures JavaScript errors, uncaught exceptions, unhandled promise rejections, and failed resource loads. Distinguishes from sibling tools like capture_console and capture_network by focusing on errors specifically.

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?

Implies usage for finding runtime JS errors and broken resources, but does not explicitly state when to use versus alternatives or provide when-not guidance.

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