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

Annotations already declare readOnlyHint, idempotentHint, and closed-world, so the safety profile is covered. The description adds real value beyond that with 'as the network actually computes them,' signaling these are the effective/authoritative computed rules rather than static documentation, which is useful nuance for interpreting the result.

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?

A single front-loaded sentence that frames the concept before listing contents. The colon-separated enumeration is listy but every item names a distinct rule domain, so nothing is wasted; a shorter phrasing could have trimmed a few words.

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?

An output schema exists, so return-value explanation is unnecessary, and a zero-param read tool needs little more. The description's scope enumeration is sufficient for correct invocation, though a note on whether rules are network-specific or cached could have added polish.

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 there is nothing for the description to disambiguate; the baseline of 4 applies. The enumerated topics describe the response content rather than any parameter, which is appropriate here.

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 tool returns (view earnings definition, commission, welcome credits, widget installation) which pins down the resource clearly, though it uses a noun phrase rather than an explicit verb like 'retrieve'. It does not name or contrast any sibling, but none of check_site/get_network_stats/list_members overlap in scope, so an agent can still route correctly.

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: enumerating the covered topics suggests calling it whenever you need commission, credit, or view-definition details. There is no explicit when-to-use statement, no prerequisites, and no mention of alternatives, leaving the agent to infer the trigger condition.

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