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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's value-add is domain framing ('Free. No income guarantee. Not MLM', anti-spam rules, 14/30-day hold periods, manual owner-approved USDC payouts) which sets expectations about what the returned content will say, but it does not describe the tool's own behavior such as whether content is static or sourced live.

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?

The description is a single dense sentence but it is front-loaded with the key qualifiers ('Free. No income guarantee. Not MLM') before the content inventory, and every clause maps to concrete program detail rather than filler. It is long only because it enumerates real subject matter.

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 static, read-only explanatory tool with no output schema and no required parameters, the description adequately tells the agent what content to expect. The only real omission is any mention of the optional language parameter, which leaves a small but recoverable gap.

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?

There is one optional parameter, 'lang', with an en/zh enum and 0% schema description coverage, and the description never mentions that the explanation is available in multiple languages. The enum values are largely self-explanatory, which keeps this at a minimum-viable 3, but the description missed an easy opportunity to compensate for the coverage gap.

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 uses a specific verb ('Explains') and a specific resource (the MoneyTools AI sales-partner/affiliate program), then enumerates its contents: services and use cases, exact payout rates, attribution, hold periods, payout mechanics, anti-spam rules and terms. That makes it clearly distinguishable from sibling actions like partner_signup or partner_stats, even though it never names them explicitly.

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: the description makes clear this is the explanatory/overview surface, so an agent can infer it should be consulted for program terms before signup or checking stats. It gives no explicit when-to-use versus partner_signup/partner_stats/partner_pitch_kit guidance and no exclusions.

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