EcoFlow MCP Server

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

No annotations are provided, so the description carries full burden. It describes the tool as a 'Get' operation, implying read-only behavior, but does not disclose critical behavioral traits such as authentication requirements, rate limits, error conditions, or what 'comprehensive status' entails in terms of response format. This leaves significant gaps for an agent to understand how to invoke it effectively.

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 a single, efficient sentence that front-loads the purpose ('Get comprehensive status') and immediately details the scope (device metrics). Every word earns its place, with no redundancy or unnecessary elaboration, making it highly concise and well-structured.

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 no annotations and no output schema, the description is incomplete for a tool that returns 'comprehensive status.' It lacks details on response structure, error handling, or behavioral constraints, which are essential for an agent to use this tool correctly. The description does not compensate for the absence of structured data, leaving significant contextual gaps.

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?

The input schema has 100% description coverage, with the parameter 'serial_number' well-documented in the schema. The description does not add any meaning beyond what the schema provides, as it does not mention the parameter or provide additional context like format examples or usage notes. With high schema coverage, the baseline score of 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?

The description clearly states the specific action ('Get comprehensive status') and resource ('EcoFlow device'), with explicit details on what metrics are included (battery level, input/output power, temperatures, all available metrics). It distinguishes itself from siblings like ecoflow_get_solar_input or ecoflow_list_devices by focusing on overall device status rather than specific aspects or listing devices.

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 implies usage when needing comprehensive device metrics, but does not explicitly state when to use this tool versus alternatives like ecoflow_get_solar_input for solar-specific data or ecoflow_list_devices for device enumeration. No guidance on prerequisites or exclusions is provided, leaving usage context inferred rather than clearly defined.

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