EcoFlow MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a configuration/write operation but doesn't mention critical behavioral aspects: whether changes are immediate or require device connectivity, if there are permission requirements, potential side effects (e.g., device restart), error conditions, or rate limits. For a mutation tool with zero annotation coverage, this is a significant 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?

The description is a single, efficient sentence that front-loads the core purpose and enumerates the key parameters without unnecessary words. Every element earns its place, making it easy for an agent to quickly understand what the tool does.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after configuration (e.g., success confirmation, error responses), behavioral constraints, or integration with sibling tools. Given the complexity of device configuration and the lack of structured safety/behavioral data, the description should provide more context about execution and outcomes.

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 fully documents all four parameters with clear descriptions and constraints (e.g., percentage ranges 0-100, AC charging power in watts). The description adds minimal value beyond the schema by listing the same three configurable parameters mentioned in the schema descriptions. Baseline 3 is appropriate when 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 action ('configure') and resource ('charging settings for an EcoFlow device'), including specific configurable parameters (max charge level, min discharge level, charging power). It distinguishes from sibling tools like 'ecoflow_get_charging_settings' by specifying a write operation rather than a read operation. However, it doesn't explicitly differentiate from other configuration tools like 'ecoflow_set_ac_output' or 'ecoflow_set_dc_output' beyond the charging focus.

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 doesn't mention prerequisites (e.g., device must be online), exclusions (e.g., not for solar settings), or comparisons to sibling tools like 'ecoflow_set_ac_output' or 'ecoflow_set_dc_output'. The agent must infer usage from the tool name and description alone.

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