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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds meaningful operational context beyond annotations: data is synced hourly via GovConAPI with latency ≤60 min and a SAM fallback every 6h. It does not cover rate limits or pagination, but given the annotations, this is a solid addition.

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 front-loaded with purpose, then filters and return fields, then use cases, then data freshness. It is dense but every sentence contributes useful information. Slightly long, but no wasted or repetitive sentences.

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?

The description covers purpose, available filters, return fields, use cases, and data freshness. Annotations cover the safety profile, and no output schema exists so return fields are described directly. Missing pagination or result-limit details, but otherwise complete for an agent to call the tool correctly.

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%, so each parameter is already documented in the input schema. The description lists the filter categories and notes they can be combined, which adds slight semantic value, but it does not add format details or constraints beyond what the schema provides. Baseline 3 is appropriate when the schema carries the parameter burden.

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 verb and resource: 'Explore and answer questions about federal contract opportunities.' It details the filters and return fields, making the tool's scope clear. However, it does not distinguish this tool from its siblings gov.digest and gov.near_expiry, which would require an agent to infer the difference from names alone.

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?

Gives clear when-to-use guidance: 'Use this when you need to research a specific market, match a capability, or compare opportunities.' It does not mention when not to use it or name alternative sibling tools, so the agent receives context but no explicit exclusions.

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