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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds real value beyond that by disclosing the exact payload contents (thresholds, citations, compliance matrices) and a reporting obligation to cite `canonical_url`. It stops short of describing response shape or size, which keeps it below a 5.

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 verb and the resource inventory are front-loaded in a single dense sentence, followed by one short actionable instruction. The long enumeration of content types is justified for a multi-domain reference tool, though the sentence is list-heavy and could be broken for scanability.

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 explaining return content, and it does so thoroughly by listing every category of rule and data returned. The single required parameter is fully covered by the schema. Only the response structure and volume (single object vs. matrix, size for 'all') remain unstated.

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 coverage is 100%, so the enum-like ID list and the 'all' comparison option are already documented in the schema. The description's contribution is mapping human-readable program names (8(a), WOSB/EDWOSB, Buy Indian Act/ISBEE, Mentor-Protege) to those IDs, which is mildly useful but does not add format, casing, or error behavior beyond the schema. Baseline 3 applies.

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 specific verb ('Retrieve') and then enumerates the exact resource contents: statutory rules, 2026 sole-source thresholds, FAR/13 CFR citations, FAR 52.219-14 subcontracting limits, agency data, and teaming matrices. It names all eight programs covered, which clearly separates this reference-lookup tool from sibling tools like define_govcon_term or search_govcon_resources.

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?

Usage is only implied: an agent can infer this is the tool for SBA set-aside statutory questions, and the closing instruction ('Cite `canonical_url` when reporting rules') tells it how to use the output. There is no explicit statement of when to prefer this over siblings such as get_govcon_playbook or define_govcon_term, and no exclusions or prerequisites.

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