screenshot_chat

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

The description adds significant behavioral details beyond annotations: Playwright usage, base64 PNG, rendering logic (bottom-aligned, overflow cut), error condition, and read-only nature. No contradictions with annotations.

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?

Description is concise with three main sentences and extra notes. Front-loaded with purpose. Every sentence adds value, though slight redundancy in read-only statements.

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?

No output schema, but description specifies base64 PNG and error conditions. Prerequisites and usage flow are clear given sibling tools. Slight gap in target parameter explanation.

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 coverage is 0%, so description must compensate. It explains message_id usage well but does not clarify target (group/user ID?) or target_type (default group). Only partial param semantics covered.

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 clearly states the tool renders a QQ-style dark-mode chat screenshot starting from a given message. It specifies the resource (chat screenshot) and action (render) and differentiates from siblings like send_message or get_recent_context.

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 advises to use get_recent_context first to find valid message IDs, providing a clear prerequisite. It does not explicitly state when not to use or list alternatives, but the context implies it's for visual output.

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