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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds meaningful context beyond them by flagging the result as 'a theoretical maximum' and scoping it to 'this week', but it never explains where 'your volume' comes from given zero input parameters, which is a notable behavioral gap.

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 short sentences, front-loaded with the applicability scope before the computed result. The trailing fragment 'A theoretical maximum, said so' is slightly informal and clipped, but it carries real information rather than filler.

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?

With no output schema, the description must convey what comes back; it does describe the outputs (points and fee cost) but not their shape, granularity, or per-venue breakdown. Combined with the unaddressed question of how user volume is determined without parameters, the definition is adequate but leaves gaps for a zero-input analytical tool.

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 schema semantics to compensate for; baseline 4 applies. The description's statement that volume is implicitly 'yours' is consistent with the empty schema but does not add further parameter meaning.

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 names a specific computation: points earned this week per dollar of fees spent, restricted to perp DEXs with a published weekly points pool. That is concrete enough for an agent to distinguish it from siblings like trading_cost (fees only) or live_airdrops (airdrop listings), although it never names those siblings 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?

The phrase 'For perp DEXs with a published weekly points pool' establishes an applicability condition, which is real guidance. However, it does not say when to prefer this over live_airdrops or farming_route, nor does it state any exclusions or prerequisites, leaving the routing decision to inference.

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