Consumo sessione

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

The readOnlyHint annotation already establishes that this is a safe read-only operation, so the description does not need to cover safety. It adds some session scoping and names token usage and screenshots as the measured data, but it does not clarify the return structure or whether the values are counts, comparisons, or both.

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 a single short sentence fragment with no wasted text and the metric context is front-loaded. Its brevity is appropriate, though the cryptic 'vs screenshots' wording slightly weakens the structure.

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 zero-parameter, read-only stats tool, the description gives a minimal indication of what is reported: session token usage and screenshots. However, without an output schema, the description should more clearly explain what the returned statistics look like and what 'vs screenshots' means.

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?

This tool has zero parameters, so parameter semantics are trivially complete. The empty schema and 100% schema description coverage mean no additional parameter explanation is required.

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 hints at session token usage and screenshots, but the phrase 'vs screenshots' is ambiguous and does not clearly state the resource or metric returned. It is distinguishable from the action-oriented browse_* siblings only because of the tool name and title, not because the description explicitly differentiates it.

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 guidance on when to use this tool instead of browse_screenshot or the other browse_* tools. The description does not mention prerequisites, expected context, or exclusions.

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