Retrieve current advertiser balance and currency for quick alerts and balance checks, avoiding heavier account or finance operations.
Lightweight current advertiser balance and currency. Use for alerts and balance checks; prefer this over kadam_adv_get_account or finance operations when you only need the balance.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.7.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
readOnlyHint=true already establishes the safe-read profile, but the description adds value beyond annotations by disclosing the returned content (balance and currency) and the 'lightweight' nature of the call. It stops short of stating freshness, currency/account scoping, or error behavior, so it falls just below a full 5.
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?
Two tight sentences, zero filler. The resource and return contents come first, the routing guidance second — appropriately front-loaded.
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?
With no parameters, no output schema, and only readOnlyHint in annotations, the description carries the remaining burden and does so: it states what is returned (balance and currency) and when to call it. Nothing an agent needs to invoke this correctly is missing.
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 tool takes zero parameters, so there is nothing for the description to clarify beyond the schema; baseline 4 applies. The description correctly implies the call is self-scoped to the current advertiser, which is useful since no scoping parameter exists.
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 names a concrete resource (current advertiser balance and currency) with an implied retrieval verb, and explicitly distinguishes itself from kadam_adv_get_account and finance operations. An agent can separate it from the 50+ siblings without opening the 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?
It gives an explicit use case (alerts and balance checks) and names the alternatives it should displace (kadam_adv_get_account, finance operations) with the selecting condition ('when you only need the balance'). Routing is fully determined.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.