Get Address Definition

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: the server serves both networks at once, the default is mainnet, and confirmation is required when network intent is unclear.

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 tight and front-loaded: a one-line purpose statement, then focused network instructions. Every sentence earns its place, and the critical network ambiguity guidance is included without fluff.

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?

For a tool with only two parameters, rich annotations, and no output schema, the description covers the main decision points: which network to use, the default, and when to ask the user. It does not describe the response shape, but the term 'definition' gives enough expectation for a simple read operation.

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%, so the description must compensate. It fully explains the network parameter, including allowed values and default behavior, but gives only minimal implicit meaning for the required address parameter ('definition of one Obyte address') without describing format, validation, or expected address style.

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 states a clear action and resource: 'Raw hub read. Returns the definition of one Obyte address.' This is specific enough to distinguish from analysis-oriented siblings like obyte_analyze_address, but it does not explicitly name any sibling or explain what 'definition' includes.

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?

Provides concrete usage context for the network parameter, including the two valid values, the default, and a strong instruction to confirm the network when the user has not specified it. It does not compare against alternative tools or give when-to-use versus when-not-to-use guidance.

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