rustchain_epoch

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

Discloses the 600-second interval and RTC rewards, which adds context beyond a simple getter. No side effects mentioned, but as a read-only tool, this is acceptable.

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: purpose first, then returns and context. No wasted words.

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?

Covers key returns and context. Output schema exists, so return format is handled elsewhere. Could mention if the epoch info is live or cached.

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?

No parameters exist, so description does not need to explain them. Schema coverage is 100% because no parameters are present.

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?

Clearly states 'Get current RustChain epoch information' with specific verb and resource. Lists return fields, distinguishing it from siblings like rustchain_balance or rustchain_miners.

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?

Implicitly suggests usage for epoch queries but does not explicitly state when to use or avoid this tool compared to alternatives like rustchain_stats which may provide broader stats.

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