MCP HydroCoder Vision

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool performs OCR and supports multiple languages, but lacks details on error handling, performance characteristics (e.g., speed, accuracy), rate limits, or output format. For a tool with no annotations, this leaves significant gaps in understanding its operational behavior.

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 extremely concise and front-loaded, consisting of just two short sentences: 'Extract text from an image (OCR). Supports multiple languages.' Every word contributes directly to the tool's purpose and capabilities, with no wasted verbiage or 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?

Given the lack of annotations and output schema, the description is incomplete for a tool performing OCR. It doesn't explain what the output looks like (e.g., plain text, structured data), error conditions, or any behavioral nuances. While the purpose is clear, the operational context is underspecified, making it inadequate for full agent understanding.

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 the input schema already documents both parameters ('imagePath' and 'language') with clear descriptions. The description adds marginal value by implying the 'language' parameter relates to OCR language support, but doesn't provide additional syntax, format details, or examples beyond what the schema specifies. This meets the baseline for high schema coverage.

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's purpose: 'Extract text from an image (OCR).' It specifies the verb 'extract' and resource 'text from an image,' with the parenthetical 'OCR' adding technical context. However, it doesn't explicitly differentiate from sibling tools like 'analyzeImage' or 'describeForCode,' which might also process images but for different purposes.

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?

The description provides no guidance on when to use this tool versus alternatives. It mentions 'Supports multiple languages,' which hints at a use case for multilingual text, but doesn't specify when to choose this over sibling tools like 'analyzeImage' or 'describeForCode,' nor does it outline any prerequisites or exclusions for usage.

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