Indexer: Historic total VTHO claimed

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds that it returns a time series (running total), but does not elaborate on data freshness, pagination, or authentication. The added context is minimal and within expectations given the annotations.

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 succinct sentences: the first explains the purpose, the second provides the endpoint. No unnecessary words. Ideal for quick comprehension.

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 simple historic data retrieval tool with one parameter, rich schema, output schema present, and complete annotations, the description is nearly sufficient. It lacks detail on output structure (e.g., time series format) but the presence of an output schema mitigates this. Slight gap in what 'running-total time series' entails.

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 description coverage is 100% with a clear enum for 'range.' The tool description mentions the endpoint template but adds no additional semantics beyond the schema. Baseline 3 is appropriate as the schema fully describes the parameter.

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 it returns a 'Running-total time series of total VTHO claimed across Stargate.' Combined with the title 'Historic total VTHO claimed,' it specifies the verb (retrieve) and resource (historic total VTHO claimed) and differentiates from the non-historic sibling getStargateTotalVthoClaimed.

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 no guidance on when to use this tool versus alternatives. Given siblings like getStargateTotalVthoClaimed, the agent must infer from names alone. No explicit when-to-use or when-not-to-use advice.

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