Firefly III MCP Server

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

Annotations indicate this is a write operation (readOnlyHint=false) and non-destructive. The description adds valuable behavioral context by explaining the mechanics of each auto-budget type (reset vs rollover behavior) and their implications, which goes beyond what annotations provide.

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 optimally structured with the core purpose front-loaded in the first sentence, followed by a clearly labeled section for auto-budget options using a scannable list format. No redundant or filler text is present.

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 complexity of the auto-budget feature (interdependent parameters: type, amount, period, currency), the description adequately explains the conceptual model and enum values. While it lacks return value documentation (no output schema exists) and error scenarios, it covers the primary functional complexity sufficiently.

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?

With 100% schema description coverage, the baseline is 3. The description adds value by expanding on the auto_budget_type enum values with slightly more detailed explanations (e.g., clarifying 'reset' resets 'to the set amount') and presenting them in an easy-to-scan list format, aiding comprehension beyond the raw schema.

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 ('Create') and resource ('budget'), and explains the core purpose ('track spending limits'). However, it doesn't explicitly differentiate from sibling tools like firefly_create_category or firefly_update_budget, which would help the agent select the correct tool.

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 implied usage guidance through the detailed explanation of auto-budget options, helping users configure the tool correctly. However, it lacks explicit guidance on when to use this tool versus alternatives like firefly_update_budget, or prerequisites for creation.

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