scout_console_logs

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

No annotations provided, and description does not address side effects or safety. It does not explain whether reading logs affects browser state or if the clear parameter's default (false) means logs persist. Minimal behavioral context.

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?

Single sentence with no redundancy. Every word contributes to the purpose.

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 simplicity (1 param, no output schema), the description is adequate but lacks details on output format, timing, or default clearing behavior. Agents may need more context for effective use.

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 100% for the single parameter, so baseline is 3. Description adds no extra meaning beyond schema's 'Clear logs after reading (default: false)'; does not clarify implications or usage.

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?

Description clearly states 'Get the last 100 browser console logs and errors', specifying verb, resource, and quantity. It effectively distinguishes from sibling tools like scout_screenshot or scout_evaluate.

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?

No guidance on when to use this tool or when to prefer alternatives. Lacks context for integration with other scout tools, such as checking logs after interactions.

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