EcoFlow MCP Server

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 retrieves data ('Get'), implying a read-only operation, but does not specify whether it requires authentication, has rate limits, or details the response format (e.g., JSON structure). For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior and constraints.

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 core purpose and includes specific data fields. There is no wasted language or redundancy, making it easy to parse and understand quickly. It effectively communicates the essential information without unnecessary elaboration.

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?

For a simple read operation with one parameter and no output schema, the description is minimally adequate. It covers what data is retrieved but lacks details on authentication, error handling, or response structure. Without annotations or an output schema, the agent might struggle with integration, though the tool's low complexity mitigates some completeness concerns.

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 single parameter 'serial_number' documented as 'The device serial number.' The description does not add any semantic details beyond this, such as format examples or validation rules. Given the high schema coverage, the baseline score of 3 is appropriate, as the schema adequately handles parameter documentation without extra value from the description.

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: 'Get solar panel input data for an EcoFlow device including current power, voltage, and daily energy statistics.' It specifies the verb ('Get'), resource ('solar panel input data'), and target ('EcoFlow device'), with concrete data fields listed. However, it does not explicitly differentiate from siblings like 'ecoflow_get_device_status' or 'ecoflow_get_raw_quota', which might overlap in functionality, so it falls short of a perfect score.

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 does not mention prerequisites, such as device connectivity or authentication, nor does it compare to sibling tools like 'ecoflow_get_device_status' for broader status checks. Without any usage context or exclusions, the agent must infer when this tool is appropriate.

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