charlotte_screenshot

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

No annotations exist, so description carries full burden. Describes save and output_file behaviors (persistence, file writing, return type differences). Not exhaustive (no mention of default return format), but adds meaningful context beyond schema.

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?

Two sentences plus brief parameter hints. Front-loaded purpose. Every sentence adds value. No redundancy.

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?

Covers main purpose, fallback role, and key behavioral differences for save/output_file. Lacks mention of default format or base64 return, but acceptable for a screenshot tool with no output schema and sibling differentiation.

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 100%, baseline 3. Description adds extra context for save (persistent artifact, metadata) and output_file (confirmation only) beyond their schema descriptions. Adds moderate value.

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?

Clearly states action ('Capture a visual screenshot') and resource. Distinguishes from sibling tools by framing as a fallback for visual content like complex visualizations, canvas elements, and images.

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?

Explicitly says to use when 'structured representation isn't sufficient' and gives concrete examples. Also advises on using save:true for persistence. Could be clearer on when not to use, but the fallback phrasing implies it's secondary.

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