getConnectBalance

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

With no annotations provided, the description carries the full burden and does well by disclosing the rate limit ('100 requests per 1m') and read-only nature. It also names the HTTP method and endpoint. It does not describe response format or potential error cases, but for a simple read-only balance lookup the key behavioral traits are covered.

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 a single, dense sentence that delivers the resource, the endpoint, the read-only safety profile, and the rate limit without fluff. Every component earns its place and the most important information is 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?

For a zero-parameter, no-output-schema tool, the description is largely complete: it states what is returned (balance), how to access it (endpoint), safety (read-only), and usage limits (rate limit). The only omission is a clearer picture of the response shape, but the low complexity and named resource keep this from being a significant gap.

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 has zero parameters, so the baseline is 4. The description still adds useful context by clarifying that the balance belongs to the connected account, making the implicit auth context concrete. There are no parameter semantics to explain beyond this.

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 states a specific verb and resource: 'Get the connected account's Stripe balance', reinforced by the exact endpoint 'GET /paygate/connect/balance'. This clearly distinguishes it from sibling tools like getConnectAccount, which presumably returns account details rather than balance.

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?

The description makes the intended use obvious from its resource name, but it does not explicitly state when to use this tool versus an alternative or when not to use it. It gives no exclusion criteria or sibling comparisons, though the unique balance-focused purpose makes misuse unlikely for a zero-parameter getter.

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