get_indexer_status

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

No annotations provided, so description carries full burden. It discloses return values (indexed height, chain tip, sync percentage, blocks/sec, ETA) and implies read-only behavior. Could mention performance characteristics or auth requirements, but return disclosure is strong.

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?

Three well-structured sentences: purpose declaration, return value specification, and usage guidance. No redundant words. Information is front-loaded with the core action.

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?

Appropriate for a simple zero-parameter status tool. Output schema exists (reducing need for detailed return description), yet description helpfully lists expected fields. No obvious gaps given tool complexity.

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?

Zero parameters present, warranting baseline score of 4 per rubric. Schema coverage is 100% (empty object), so no additional parameter semantics needed.

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?

Clear specific verb 'Check' + resource 'blockchain indexer sync progress'. The term 'indexer' effectively distinguishes this from sibling tools like get_node_status or get_blockchain_info.

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 states when to use: 'to check if the indexer is running and how far along the initial sync is'. However, lacks explicit 'when not to use' guidance or named alternatives among the many similar status-checking siblings.

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