Ordiscan: getLatestRunes

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

Annotations already indicate readOnly, non-destructive, idempotent, open world. Description adds that it returns 'latest' Runes, implying ordering, but no detail on pagination, rate limits, or how many results. Adequate but not rich.

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 with no filler. First sentence states purpose, second gives usage guidance. Highly efficient and front-loaded.

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 no output schema and three parameters, description could hint at return structure (e.g., list of Rune token objects). Also fails to differentiate from closely related siblings like getTopRunesBy* or getRunesActivity. Adequate for simple tool but incomplete.

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 0%. Description does not explain any parameter beyond the tool's purpose. 'sort' enum values are inferable, but 'after' and 'before' are opaque – likely pagination or time filters but no clarification.

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 clearly states the tool lists latest Rune tokens for market discovery and browsing, and explicitly distinguishes from personal balance checks. The verb 'List' combined with resource 'Rune tokens' leaves no ambiguity.

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?

Explicitly says to use for new/trending Runes and NOT for checking personal balance. This provides clear when-not. However, it does not mention alternative sibling tools like getRuneBalances or getTopRunesByVolume for more specific use cases.

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