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

With no annotations, the description carries the safety burden and does so: 'Read-only' declares the operation is non-mutating, and 'Payout requests themselves can only be made in the app' proactively closes off an action an agent might otherwise attempt. Auth requirements and rate limits are still unmentioned, keeping it below 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?

One compact sentence packs the field inventory, followed by the payout limitation and the read-only flag. The comma-heavy list of totals is dense but every item carries information; the important constraint (read-only) is placed at the end rather than 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?

No output schema exists, so the description must describe the return shape, and it does by naming each returned metric group plus per-link stats and payout statuses. Combined with the zero-parameter simplicity and the read-only disclosure, an agent has enough to call and interpret it.

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 tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate beyond confirming the tool needs no input.

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 enumerates exactly what the overview contains (commission %, minimum payout, totals, referral links with stats, payout request statuses), which distinguishes it from create_referral_link / update_referral_link / get_referral_share_card by scope. The verb is implicit rather than stated ('overview'), and sibling tools are never named, so it stops short of a 5.

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?

Usage is only implied: an agent can infer this is the aggregate view to call before drilling into referrals or links. There is no explicit when-to-use versus list_referred_users or get_referral_share_card, and no stated prerequisites.

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