console

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

readOnlyHint=true already tells the agent this is a safe read. The description adds two useful traits beyond that — the window is only 'recent' messages, and uncaught exceptions are included alongside logged messages. It says nothing about ordering, pagination, or whether the buffer is cleared on read, so the added context is modest.

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?

A single front-loaded sentence with no filler; the resource and scope appear immediately. It is efficient, though the brevity comes at the cost of any parameter or behavioral detail.

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 simple two-parameter read tool with no output schema and a readOnlyHint, the description is adequate at the top level. However, it leaves the filter and limit semantics completely unexplained, which is the main thing an agent needs in order to call it correctly.

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 0% and there are two parameters, limit and filter, neither of which the description mentions. An agent cannot tell from the text whether filter matches message text, severity level, or source, nor what limit defaults to — the description does not compensate for the coverage gap.

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?

Names a specific resource (console messages plus uncaught exceptions) from a specific source (the client page), which is enough to tell it apart from siblings like network or metrics. It is a noun phrase rather than a verb, but the retrieval intent is unambiguous.

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?

There is no statement of when to reach for this tool versus alternatives such as network, metrics, state, or eval. The agent must infer that console diagnostics belong here and network/errors elsewhere, with no exclusions or prerequisites given.

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