dogecoin_get_transaction_history

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

No annotations are present, so the description must disclose behavioral traits itself. It only says 'Get transaction history' and omits useful details such as pagination defaults, ordering, transaction types (incoming/outgoing), or any network defaults. This is minimal and does not enrich the agent's understanding beyond the tool's name.

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 a single, direct sentence with no extraneous words. It is front-loaded with the action and resource, achieving clarity in one breath.

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 simple read-only listing tool with three well-documented parameters, the description is minimally viable. However, it lacks details about pagination behavior or response format, which would be useful given the absence of an output schema and annotations. It covers the core intent but not the full context.

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?

The input schema provides descriptions for all three parameters (address, limit, offset), giving 100% coverage. The description adds no additional parameter-level meaning, which aligns with the baseline of 3 when the schema is fully descriptive.

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 uses a specific verb 'Get' with an explicit resource 'transaction history' and target address, clearly identifying its purpose. It distinguishes itself from sibling Dogecoin tools like dogecoin_get_balance and dogecoin_get_network_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?

No guidance is provided on when to use this tool versus alternatives, nor any exclusions or contextual hints. The description merely states what it does without explaining when it is preferable to similar chain-specific transaction history tools.

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