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

With no annotations, the description carries the full burden, yet it only discloses the output range and badge categories. It does not reveal how tier weighting works, what threshold produces each badge, how zeros are handled, or the role of the optional recent30dHits parameter, leaving the computation opaque.

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?

The description is a single, front-loaded sentence that names outputs before inputs and contains no filler. It is efficient, though it may be too brief to carry the behavioral and parameter information the agent needs.

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 tool has nested inputs, an optional parameter, no output schema, and no annotations. The description does not explain how to populate hitsByTier, what recent30dHits influences, or where badge boundaries lie, making it incomplete for confident invocation in varied scenarios.

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 by explaining parameters, but it only gestures at 'tier-weighted funding-article hit counts.' It never describes recent30dHits or the distinct tier_1, regional, vertical, and presswire keys, so an agent gets little help understanding what values to pass or how they combine.

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 opens with a direct compute verb and names the exact outputs: funding_momentum_score and a badge. It clearly identifies the tool's topic and differentiates it from most compute_* siblings, though it does not explicitly contrast with any specific alternative.

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?

The description implies this tool is used when funding-momentum scoring from tier-weighted article hit counts is needed. However, it provides no explicit when-to-use conditions, exclusions, or alternatives among the many similar compute_* sibling tools.

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