deepseek_check_balance

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new operational context: it requires DEEPSEEK_API_KEY and takes no arguments, and that telemetry is in-memory (session-scoped, likely not persisted). It stops short of noting that the balance portion makes an authenticated network call that can fail on missing/invalid keys.

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?

Front-loaded with the primary verb+resource and kept to three short sentences. The second sentence partially restates the first ("Verify account funds and monitor session usage" vs the opening line), which is mild redundancy but also serves as the usage statement.

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 no-argument read tool with an output schema, everything essential is present: purpose, auth prerequisite, arity, and routing away from siblings. The only soft spot is "in-memory session telemetry", which leaves ambiguous whose session is measured and when the counters reset.

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?

Zero parameters, so the baseline is 4. The description reinforces this with "Takes no arguments", which prevents an agent from hunting for a currency or session-id parameter that does not exist.

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?

States a specific verb+resource pair ("Check DeepSeek account balance (CNY/USD)") plus a second explicit capability ("in-memory session telemetry"), and names the sibling tools it is not for. An agent can distinguish it from the deepseek_search/fetch family without opening any schema.

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?

Gives explicit positive context ("Verify account funds and monitor session usage") and an explicit exclusion with named alternatives: "Do not use for search or retrieval (use deepseek_search or deepseek_fetch)". Both when-to-use and when-not-to-use are covered.

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