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

With no annotations, the description carries the full behavioral burden and does so well: it discloses the data sources (verified rows only: job-board work, contribution quality records, reputation bond ledger), the exact weighting scheme, and the insufficient_data/null-no-guessing policy. These are material traits an agent cannot infer from the schema.

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?

Front-loads the purpose and formula before the behavioral caveats, and each sentence carries information (formula, sources, return shape, failure mode, sibling routing). The formula line is dense but earns its place for a scoring tool.

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?

An output schema exists, so return-value detail is technically optional, yet the description still names what is returned (score, components with sample counts and window, matched data keys). Combined with the scoring formula and failure mode, an agent has enough to call and interpret the tool; only parameter format is under-specified.

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 single 'agent' parameter has 0% schema description coverage, and the description only implies an agent identifier via 'for one agent' and 'matched data keys'. It does not clarify the expected format (id vs name vs address) or lookup semantics, so it adds only marginal meaning beyond 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?

States a specific resource (Verified Job Performance Score for one agent), gives the exact formula and components, and explicitly distinguishes itself from the sibling solvscore_vjps_top leaderboard variant. An agent can identify the tool's scope without opening the schema.

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?

Explicitly routes the agent to solvscore_vjps_top for the ranked leaderboard and frames VJPS as complementing the SolvScore trust level. It lacks a fuller when-not-to-use statement (e.g., what to do when the agent is unknown or data is thin beyond the null return), so it is clear but not exhaustive.

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