ghl_saas_get_location_wallet_balance

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds meaningful context: the agency-token security requirement, the OAuth scope, and that it returns a resource object with balance details. Auth preconditions are exactly the kind of context annotations don't supply.

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 token requirement is stated twice (the ALL-CAPS header and the later 'Requires an Agency (company-level) token') plus redundant metadata (version header, source file). Front-loaded and readable, but the repetition costs it.

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 simple two-param read tool with full schema coverage and no output schema, the definition covers auth requirements, the endpoint, and a rough return shape. Adequate and complete enough to invoke correctly.

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?

Schema coverage is 100% and both companyId and locationId are documented in-schema, so the description needn't duplicate them. The endpoint template reinforces which param maps to which path segment but adds no new semantics; baseline 3.

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 and resource ('Fetch the wallet balance for a specific location') with an explicit endpoint template. An agent can distinguish it from update_location_wallet_balance and list_location_wallet_transactions from the verb+scope alone.

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?

Conveys the key precondition (agency/company-level token, OAuth scope saas/company.read), but gives no explicit when-to-use vs siblings like list_location_wallet_transactions or update_location_wallet_balance. Usage is only implied by the name.

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