get_console_errors

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

Discloses that clearing the buffer is the default behavior and that entries are captured passively. Without annotations, this description adequately informs the agent of key behaviors, though additional details (e.g., auth, rate limits) are missing.

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?

Three concise sentences that front-load the primary purpose, include key behavioral details, and provide usage guidance. Every sentence adds value with no redundancy.

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?

Covers the tool's purpose, behavior, and usage context effectively given the simple parameter set and missing output schema. Could mention the output format (e.g., array of errors) to be fully complete, but this is not critical.

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 has 100% coverage with descriptions for both parameters. The description adds meaning by explaining the 'clear' parameter's default and the operational context ('since last read'), providing value 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 the tool returns browser console output including errors, warnings, and logs. Specifies passive capture and default clearing behavior. Positions it as the first debugging step, distinguishing its purpose from other 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?

Explicitly recommends it as the first stop when debugging a broken page and notes no steps are required. Does not mention when to avoid it or alternatives, but the context is clear for common debugging scenarios.

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