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

Annotations already indicate read-only, idempotent, and open-world hints. The description adds the behavioral detail of synced status definition (synced true when block == header height), and clarifies it requires no sign-in and has no parameters, which goes beyond annotations to set user expectations.

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?

The description is well-structured, front-loading the core purpose (health and sync check) and then providing details in a logical order. It efficiently communicates all necessary information without redundancy.

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 the tool's simplicity (no parameters, clear purpose) and the rich annotations plus output schema, the description covers everything an agent needs to call it correctly and interpret its role. It even provides a usage sequence recommendation.

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?

With zero parameters and 100% schema coverage, the schema trivializes parameter documentation. The description explicitly states 'no parameters,' which is redundant but harmless, and adds value through the overall purpose explanation rather than parameter-specific details.

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's purpose: checking node health and sync status, listing specific attributes (version, block height, etc.). It distinguishes itself from siblings by emphasizing it's a readiness check before using data operations like read_record or writing with register_identity.

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?

Explicit guidance is given: call this tool first in a session to confirm node health before trusting data operations or performing writes. It also names the specific sibling tools that depend on this check, providing clear when-to-use context.

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