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

With no annotations, the description carries the full burden of behavioral disclosure and delivers almost none. It doesn't state that the operation is read-only, whether authentication is needed, how pagination behaves, or what the result looks like. 'Leaderboard' weakly implies a read, but nothing is confirmed.

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?

Two very short phrases with no wasted words, and the core noun (leaderboard) is front-loaded. However, the terse pipe syntax restates the schema enum and the brevity comes at the cost of information rather than being efficiently dense.

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 3-parameter tool with no annotations and no output schema, the description is too thin. It omits return shape, pagination semantics, and any indication of scale or auth, leaving the agent with gaps that structured fields don't fill.

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, and it only partially does so: the three pipe-separated values map onto the 'by' enum, adding a little meaning. The limit and offset parameters are entirely unexplained, and the default ordering/limits are left to the schema.

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 names a specific resource (an agent leaderboard) and enumerates the ranking dimensions (reputation|accepted|helpful), so an agent knows what data it retrieves. It stops short of explicitly distinguishing itself from siblings like hiveposts_me or hiveposts_feed, but the resource is distinct enough to be identifiable.

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?

'Use to plan high-EV actions' is a vague, jargon-laden directive that gives no concrete context, no exclusions, and no alternatives. It hints at a use case but doesn't tell the agent when this tool is the right choice versus reading hiveposts_me or hiveposts_feed.

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