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

readOnlyHint=true already tells the agent this is a safe read; the description adds genuine context by disclosing that the response also carries an eligibility signal for recording new payments, which the schema does not reveal. It still omits the solo-coach restriction edge case (what happens for org-managed clients) and any ordering or volume characteristics, so it stops short of rich behavioral context.

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?

One compact sentence with no filler, and the resource is front-loaded before the secondary eligibility clause. Minor awkwardness in the parenthetical and the 'and whether...' construction, but nothing wasted.

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 output schema, the description carries the burden of describing return values, and it only sketches them ('payments recorded' plus an eligibility flag) without field-level detail, ordering, or whether the list is bounded. Adequate to select the tool, not complete enough to know what comes back.

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 the single required clientId is documented as a User _id sourced from list_clients, so the description adds no parameter detail beyond it. 'For one client' merely restates the parameter's existence, which matches the baseline 3 for a fully described schema.

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 resource (desk cash/UPI payments recorded for one client) plus an extra computed element (whether new payments can be recorded), which is more than a restatement of the name. It does not distinguish itself from close siblings such as list_client_payments or record_coach_desk_payment, so an agent must infer why this read exists alongside them.

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 phrase 'a solo coach' implies the applicable context (non-organization coaches) and 'one client' implies the single-client scope, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent facing list_client_payments, list_payments and list_organization_payments gets no routing guidance.

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