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

Annotations already cover read-only, idempotent and non-destructive behavior, so the safety profile is handled. The description adds genuine context beyond the annotations: 'deterministic' (same input yields same signals) and 'FREE beta' (cost/availability status). It does not disclose output shape or limits on text size.

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 compact sentences that front-load price/status and then the core capability. 'FREE beta' is marketing-leaning but does convey actionable availability information; nothing is redundant.

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 single-input screening tool with no output schema, the description is adequate but leaves the return shape undefined — an agent cannot tell whether it gets booleans, matched snippets, or a score per signal category. The basic-vs-evidence distinction against its sibling is also unexplained.

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?

One parameter at 0% schema description coverage, so the schema offers only min/maxLength constraints. The phrase 'in supplied tender text' implies the single 'text' input is the tender document to screen, which adds some meaning, but no format or size expectations are stated.

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 ('screening') and resource ('supplied tender text'), and enumerates the signal categories checked: set-aside, NAICS, PSC, security-clearance, dates. The 'basic' suffix plus the sibling 'tender_preflight_evidence' implies a tier distinction, though the description never explains it.

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?

No explicit when-to-use or when-not-to-use guidance. The agent must infer from the 'basic' vs 'evidence' naming convention which tool to pick, and nothing states prerequisites or the alternative path.

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