Indexer: Stargate VET delegated by period

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint as false, so the safety profile is clear. The description adds value by explaining the time-series nature and listing allowed period values, but does not reveal edge cases like behavior on invalid input.

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: first defines purpose and lists periods, second states utility. No redundant information; front-loads key details.

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?

The description is sufficient for a simple read-only tool with an output schema. It explains the resource and parameter, but could mention that it returns aggregated delegation data and possibly default behavior or limits.

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 schema describes the period parameter as 'Time period to aggregate by…'. The tool description adds value by listing the specific allowed period values (DAY, WEEK, MONTH, YEAR, ALL), which are not present as enums in the schema.

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 the tool returns a time-series of VET delegated via Stargate, and lists the specific period values (DAY, WEEK, MONTH, YEAR, ALL). This distinguishes it from siblings like getStargateVetStakedByPeriod and getValidatorDelegations.

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 indicates the tool is useful for tracking delegation flows over time, providing context for when to use it. However, it lacks explicit guidance on when not to use it or how it differs from related tools like getStargateVetStakedByPeriod.

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