solvscore_vjps_top

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

With no annotations supplied, the description carries the disclosure burden and does add real behavior: '[FREE]' flags cost, 'Scores refresh on the 6-hour SolvScore sweep' discloses data staleness, and 'ranked' discloses ordering. It stops short of stating read-only safety, pagination behavior, or a maximum reachable rank, which keeps it below a 5.

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 sentences with the resource and ranking front-loaded in the opening clause, so the most decision-relevant fact arrives first. The middle clause about 'trust level and the delivered-work record in one call' is somewhat padded but still conveys buyer value, so nothing is seriously wasted.

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 leaderboard with one optional parameter and no output schema, the description is close to adequate: it names the metric, the joined trust score, the per-row components, and the refresh cadence. The remaining gap is that the only parameter and the result set size are left entirely unexplained, so an agent cannot reason about how much data it will receive.

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% for the single 'limit' parameter, and the description never mentions it, its default of 20, or any cap on how many rows can be returned. The description partially compensates by explaining what each row contains ('full component breakdown'), which is why this sits at baseline rather than lower.

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?

Names a specific resource and ordering: a ranked leaderboard of agents by Verified Job Performance Score, joined with SolvScore trust scores. An agent can grasp the payload immediately, but the description never distinguishes it from the closely-related sibling solvscore_vjps (single-agent lookup) or from get_leaderboard/data_leaderboard.

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?

Usage is only implied through the phrase 'so a buyer can see both the trust level and the delivered-work record in one call', which hints at a buyer-side due-diligence scenario. There is no explicit when-to-use versus solvscore_vjps, no when-not, and no stated prerequisites, so the agent must infer the selection rule.

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