Indexer: Stargate total VTHO generated

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds value by clarifying 'aggregate produced, whether or not claimed' and 'Returns a numeric value encoded as a JSON string', which are behavioral details beyond annotations. No contradictions.

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, no redundant words. The first sentence clearly states the core purpose, and the second adds return format and parameter hint. Front-loaded and efficient.

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, the description adequately covers the function's purpose, aggregate nature, optional historical parameter, and return format. It provides sufficient context for a simple read-only tool, though it could explicitly mention the default latest block behavior.

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 mentions 'Optional: blockNumber for historical snapshots', which essentially mirrors the schema's own description. No additional parameter meaning is added beyond what the schema already provides. Baseline 3 is appropriate.

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 clearly states 'Fetch the total VTHO generated by Stargate delegations from validators’ block rewards', specifying the resource (total VTHO generated) and action (fetch). It distinguishes this from sibling tools like getStargateTotalVthoClaimed and getStargateTotalVetStaked by highlighting 'generated' vs 'claimed' and 'VTHO' vs 'VET'.

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 description provides a usage hint: 'Optional: blockNumber for historical snapshots', which advises when to use the blockNumber parameter. However, it does not explicitly compare to siblings like getStargateTotalVthoGeneratedHistoric or explain when to use this tool over others. The context of sibling tools implies differentiation by metric, but more explicit guidance would improve.

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