h1_get_earnings

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'List earnings.' only restates the tool's action and gives no information about pagination behavior, response format, error cases, or whether this is a safe read-only operation. This is even more minimal than typical low-scoring examples.

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?

'List earnings.' is extremely brief, but this is under-specification rather than effective conciseness. The description omits essential context and does not organize any usable information, so the brevity does not serve the agent.

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?

This is a paginated list tool with no output schema, but the description does not explain what earnings are being listed, how pagination works, or what the response contains. The schema hints at page_size and page_number, but the overall tool behavior remains unexplained.

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%, and the description does not mention page_size or page_number. While the parameter names are somewhat self-explanatory, the task requires the description to compensate for low schema coverage, and it completely fails to do so.

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 provides a clear verb and resource: 'List earnings.' This is minimally clear, but it lacks specificity about whose earnings or what scope. It does not distinguish itself from sibling tools like h1_get_payouts or h1_get_balance, which may also involve monetary amounts.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or context for when 'list earnings' is the appropriate choice. The agent is left without decision criteria.

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