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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description is not obligated to restate that. It does add non-obvious expectations: the output is 'descriptive disclosure, not a certification,' and it is explicitly out of scope of the GSA LLM-contractor rule — useful framing for interpreting the response.

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-loaded with the core purpose in the first clause, followed by qualifying detail. It runs four dense sentences with regulatory jargon and ALL-CAPS emphasis, which is heavier than needed, but each sentence carries distinct content (purpose, provenance mechanism, scope claims, usage triggers) rather than filler.

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?

With no output schema, the description carries the burden of conveying what comes back, and it does — provenance chain-of-custody details, US-source status, no PII ingest, no model training, regulatory scope. An agent knows what this call yields. Minor gap: it does not state the response form (structured doc vs. prose).

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 tool takes zero parameters (empty object schema, 100% coverage), so the baseline of 4 applies. The description adds no parameter guidance, but none is needed for a no-arg posture lookup.

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 ('Return') and a specific resource ('JYOTINT's data-handling, PROVENANCE & governance posture'), then frames it as the answer to a concrete question ('is this source safe to read / cite / ingest?'). No sibling tool in the list covers governance/compliance posture, so the definition is self-differentiating.

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?

Ends with an explicit trigger list: 'Use for compliance / data-handling / provenance / can I trust this source questions.' This gives a clear when-to-use context, though it names no alternative tool and gives no when-not-to-use exclusion (e.g. versus get_calibration_and_integrity or search_sealed_forecasts).

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