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

Annotations declare readOnlyHint=true, and the description adds useful context beyond this: it specifies the data source (USAspending.gov top-100), the comparison window (45-day vs prior 45-day), weekly update cadence, and the leading-indicator relationship. No contradictions with annotations are present.

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 compact—two substantive sentences plus a short update note. It front-loads the core output, then use cases, then update frequency. Every clause adds specific value with no fluff or repetition.

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 tool with one optional parameter and no output schema, the description covers the main return fields and use contexts effectively. It could be more complete by explicitly stating the default behavior when 'days' is omitted or describing the response shape for history mode, but the schema covers the parameter semantics.

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 100% for the only parameter 'days', and the schema already explains the history behavior and tier requirement. The main description adds no additional parameter details, so the baseline of 3 applies since the schema does the heavy lifting.

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 begins with a specific action: 'Returns a 0-100 federal prime-contract award momentum score' and identifies the resource (USAspending.gov data) and output fields (award_momentum_score, recent_vs_prior_ratio). It clearly distinguishes this tool from generic data tools by specifying the exact metric and source.

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 provides explicit 'Call when' scenarios: federal procurement trends, accelerating/slowing awards, defense contractor demand, GovCon spending, and timing forecasts. It does not mention when not to use the tool or name alternatives, so it earns a 4 rather than a 5.

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