simplepractice_get_billing_overview

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

Annotations already declare readOnlyHint=true, so no contradiction. The description adds account scoping and a performance trait (cheaper), but doesn't disclose other behaviors such as rate limits or data freshness. This is comparable to the baseline for read-only tools with annotations.

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 with zero wasted words. The primary function is front-loaded, and the second sentence provides a clear usage hint. Perfectly sized for a zero-parameter overview tool.

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 zero-parameter tool with no output schema, the description sufficiently explains the return content (balance due, per-category counts) and scope. It could mention what categories are included, but that may be overkill; the current text is complete enough for an agent to decide and call it appropriately.

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?

There are zero parameters and the schema is effectively empty (100% coverage). The description adds semantic value by explaining what the tool returns, which serves as the only parameter-related info needed. Baseline for zero params is met.

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 exactly what it returns (balance due, per-category counts) and scopes it to the Client Portal account. The verb is implicit but the resource and output are clear, and it distinguishes from detailed list tools like list_billing_items by being an aggregate overview.

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 gives a use case: cheaper than paging the billing collections when you only need to check whether anything is there. While it doesn't name the sibling, the phrase clearly points to the list-based alternative, giving the agent a decision rule.

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