Get balance

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

Annotations already carry readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral value by declaring what the response contains in the absence of an output schema, but it says nothing about authentication requirements, whether the balance is live or cached, or any rate limiting on this open-world endpoint.

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 sentences, no filler. The return contents are front-loaded, then the usage triggers follow in a compact clause separated by commas. Every phrase earns its place, and the 'valid sender_name for SMS' detail prevents a downstream parameter error.

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 input parameters and no output schema, the description carries the burden of describing returns and it does so across four named fields, plus practical usage contexts. It is slightly incomplete in not clarifying the relationship to get_account or whether sub-customer context matters for the returned customer ID.

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 no parameter semantics to clarify and the baseline of 4 applies. The description correctly implies no inputs are required, letting an agent call it directly without gathering arguments.

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 gives a specific verb+resource ('Get ChatPush account balance') and then enumerates the additional payload (customer ID, dispatch routing channels, registered sender names), so an agent knows exactly what comes back. It does not distinguish itself from the sibling get_account, which plausibly overlaps on customer ID and sender names — that is the main clarity gap.

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?

Three concrete triggers are supplied: the user asks how much money is left, a large mailing is about to be sent, and a valid sender_name is needed for SMS. That is actionable when-to-use guidance. It stops short of a 5 because no exclusion or explicit alternative is named (e.g., when to prefer get_account over this tool for account-level details).

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