get_denom_owners

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

Description says 'get all holders' but input schema shows pagination (page, limit), implying results are paginated and not all at once. This inconsistency is misleading. No disclosure of ordering, rate limits, or behavior for zero holders.

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?

Single sentence is concise but lacks necessary details about pagination and parameters. Efficiency is good, but at the expense of completeness.

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?

Despite having an output schema, the description omits key context about pagination behavior and response format. For a paginated list tool, essential information is missing.

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 denom, page, or limit. While parameter names are somewhat intuitive, the description fails to clarify that page and limit control pagination, which is crucial for usage.

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 it retrieves holders for a token (denom). The name and description align, and it distinguishes from sibling getters like get_balance or get_account. However, 'token' could be ambiguous without context.

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 on when to use this tool versus alternative list tools or other getters. Does not provide conditions for use or mention pagination behavior.

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