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 mentions the tool is for 'debugging' and accessing 'raw' data, implying it might return verbose or technical information, which adds some behavioral context. However, it lacks details on potential side effects (e.g., if it's read-only, which is implied but not stated), error handling, or rate limits, leaving gaps in transparency.

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 two sentences, front-loaded with the core purpose and followed by usage context. Every sentence earns its place by providing essential information without redundancy, making it efficient 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 the tool has no annotations and no output schema, the description is somewhat complete for a read operation, covering purpose and usage. However, it lacks details on what the raw data includes (e.g., format, structure) or potential limitations, which would be helpful for an agent to interpret results. This makes it adequate but with clear gaps in context.

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 schema already documents both parameters (serial_number and filter) with descriptions. The description does not add any additional meaning or examples beyond what the schema provides, such as elaborating on the filter parameter's usage. Thus, it meets the baseline of 3 where the schema does the heavy lifting.

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 verb 'Get' and the resource 'all raw quota/parameter data from an EcoFlow device', making the purpose specific. It distinguishes from siblings by mentioning 'device-specific parameters not covered by other tools', which helps differentiate it from tools like ecoflow_get_device_status or ecoflow_get_solar_input that might provide more processed or specific data.

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 clear context for when to use this tool: 'Useful for debugging or accessing device-specific parameters not covered by other tools.' This gives guidance on its primary use cases. However, it does not explicitly state when not to use it or name specific alternatives, such as preferring ecoflow_get_device_status for general status checks, which prevents a score of 5.

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