session_console

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

There are no annotations, so the description carries the behavioral burden. It discloses the active-tab scope, the message types returned, and the session_start prerequisite. It does not state whether the call is read-only or whether it consumes/clears console messages, but the reading intent is reasonably clear.

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 short and front-loaded with the core meaning, and the second sentence adds a valuable prerequisite. It is appropriately concise, though slightly terse.

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 an output schema exists, return-value detail is not needed. The main missing piece is parameter behavior for 'limit', as well as any explicit caution about requiring an active tab/session. It is adequate for a simple console-read tool, but not comprehensive.

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 input schema has a single 'limit' parameter with 0% schema description coverage, and the description does not mention the parameter at all. Since the description is supposed to compensate for low schema coverage, this is a clear gap, even though 'limit' is somewhat self-explanatory.

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 that the tool exposes the JS console messages (error/warning/log) of the active tab, which is a specific resource and function. It is distinguishable from sibling tools like session_network or session_text, though it is phrased as a noun phrase rather than an explicit verb such as 'get'.

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?

It explicitly says 'Требует session_start', giving the key prerequisite for use. However, it does not say when to prefer this over alternatives or when not to use it, leaving some usage context implicit.

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