Stargate: Total VTHO claimed by account

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

Description adds endpoint detail and filter semantics beyond annotations which already declare readOnly, idempotent, and non-destructive. No contradiction; transparency is adequate for a read query.

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 concise sentences, front-loaded with the endpoint path, no extraneous words or redundancy.

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?

Given the presence of an output schema and high parameter coverage, the description sufficiently explains the tool's purpose and filter options. Could note the return type, but output schema likely handles that.

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?

Schema coverage is 100%, and the description adds value by explaining the filter values (LEGACY vs DELEGATION) more concretely than the schema's generic descriptions.

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?

Description explicitly states 'Get total VTHO claimed by a given account' and includes the endpoint path, distinguishing it from sibling tools like getStargateTotalVthoClaimed (global) and getStargateTotalVthoClaimedByAccountToken (by account+token).

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?

Describes the optional rewardsType filter with clear explanations of LEGACY and DELEGATION values, and notes that omitting the filter includes all rewards. Does not explicitly compare to siblings, but context is clear enough for selection.

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