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

readOnlyHint=true already establishes the safety profile, and the description adds genuinely new behavioral context: concrete rate limits (60 requests/minute, 1000 per 24 hours) and the fact that each call consumes one request. That is useful capacity-planning information an agent cannot get from the annotations. It stops short of describing auth needs or failure behavior, so it is not a 5.

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 compact sentences, with the core purpose front-loaded and the operational constraint appended; nothing is redundant. The phrase 'The vendor limit' is slightly confusing on a client-facing tool, which keeps it from a 5.

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 read-only lookup with no output schema and full schema coverage, the definition supplies everything needed: what is returned, the addressing id's source (smartaccounts_list_clients), optional filters, and rate limits. Return-value detail is not required here and the safety profile is carried by annotations.

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 description coverage is 100%, so all three parameters (id, balance_date, fetch_details) are already documented in the schema with format and defaults. The description adds only the softer notion that the date is 'past' and that details are 'open documents', which does not go meaningfully beyond the schema. Baseline 3 applies.

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 and scope: 'the outstanding balance of one client', with the upstream endpoint (purchasesales/clients:getbalance) for anchoring. An agent can immediately tell this reads a single client's balance rather than a list. It does not explicitly name the sibling smartaccounts_get_vendor_balance as the alternate resource, so differentiation is by resource name 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?

The description hints at optional usage ('optionally on a past date and with the open documents'), which tells the agent these are discretionary. But there is no explicit when-to-use guidance, no mention of when the vendor-balance sibling should be used instead, and no prerequisites or error conditions.

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