extract_text_from_screenshot

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

No annotations are provided, so description carries full burden. It discloses scope (OCR for code/terminal/docs) and non-goals, but fails to disclose output format, whether bounding boxes/layout are preserved, accuracy limitations, or behavior on poor images. For a no-output-schema tool, this is a substantive gap.

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?

Four sentences, front-loaded with purpose, each sentence adds distinct information (definition, when-to-use, specialties, exclusions). No fluff; 'advanced OCR capabilities' is slightly filler but harmless.

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 purpose, usage, exclusions, and parameter coverage via schema. However, with no output schema and no mention of return format or failure behavior, an agent cannot fully anticipate tool output. Given moderate complexity, this is a clear gap.

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%, so all three parameters (image_source, prompt, programming_language) are already documented. Description adds minor context about OCR specializations that hints at prompt/language usage, but no syntax-level detail, so baseline 3 is appropriate.

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 opens with specific verb+resource: 'Extract and recognize text from screenshots using advanced OCR capabilities.' It clearly distinguishes from siblings by explicitly listing exclusions (UI design conversion, error diagnosis, diagram understanding), making purpose unambiguous.

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 states when to use: 'ONLY when the user has a screenshot containing text and wants to extract it.' Provides positive context (code, terminal output, documentation) and a clear 'Do NOT use for' list that semantically maps to sibling tools.

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