Check Pollinations Balance

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds critical context beyond that: the requirement for POLLINATIONS_API_KEY in the MCP client's env block, and detailed HTTP error semantics (401/403/402). This equips the agent for real-world deployment and troubleshooting.

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 well-structured with clear sections for purpose, usage timing, auth, args, returns, and errors. Every sentence conveys necessary information without fluff or redundancy, making it dense yet easily parsed.

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's simplicity (one optional parameter, read-only, no output schema), the description covers all relevant aspects: what it does, when to use it, required environment setup, what it returns, and error handling. An agent has everything needed to invoke it correctly and interpret results.

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 already fully describes response_format with enum values, default, and a description. The tool description's arg explanation ('markdown for readable balance output, json for raw account/budget response') essentially restates the schema's description without adding new meaning, so it meets the baseline but adds no extra semantic value.

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 uses a specific verb ('Check') and names the exact resource ('Pollinations pollen balance or API key budget') plus the underlying endpoint ('/account/balance'). This clearly differentiates it from the sibling generation and model-listing tools.

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?

Explicitly states when to use: 'Use this before expensive image/video generation when the user asks about available pollen, credits, budget, or why a generation may be failing with payment/balance errors.' This gives actionable, context-rich guidance that an agent can directly apply.

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