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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world call, so the safety burden is lifted. The description adds genuinely useful behavioral context by specifying the accounting window ('this month') and the currency of earnings (USDT). It does not state whether memory allowance resets monthly or what happens at exhaustion, which would be the most decision-relevant detail for a self-funding agent.

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 sentences, front-loaded with the returned data and closing with the agent-facing rationale. The first sentence is a comma-spliced list without a main verb, which is slightly awkward but compact and wastes no 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?

For a zero-parameter tool with no output schema, the description must carry the return-value burden, and it does list the four data groups. It is still thin on framing: units, whether usage is a count of bytes or entries, and how 'left this month' is computed are all left implicit. Adequate to select the tool, incomplete for interpreting its output.

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 no parameter semantics for the description to compensate for. Baseline 4 applies; nothing in the description misleads about inputs.

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 reports: plan, monthly permanent-memory (Arweave) usage and remaining allowance, referral earnings in USDT, and the referral link. The resource is unambiguous even without an explicit verb. It does not, however, explicitly distinguish itself from siblings like 'plans' or 'my_deals', which surface adjacent account data.

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 closing line 'Useful for autonomous agents that fund their own memory' implies a usage context, but there is no explicit when-to-use rule, no when-not guidance, and no named alternative. An agent must infer that it calls this to check quota or earnings before invoking buy_plan or memory_write.

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