describe_stig_content_sync

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

Beyond annotations, the description discloses 'Read-only, local static content — no database, network, or API call,' which adds critical detail about side effects. It also reveals that compliance_api_available is 'always false' and explains why_no_api, making behavioral traits fully transparent without contradicting the readOnlyHint.

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?

Though the description is long, every sentence serves a purpose: purpose, parameter confirmation, return fields with explanations, behavioral guarantees, and routing guidance. It is front-loaded with the verb and resource, and the structure allows quick scanning for key facts without redundancy.

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 is fully self-contained for an agent: it lists all return fields with in-line explanations (compliance_api_available, why_no_api, content_sources, mechanism, routing_note, importer_status), states no side effects, and provides routing guidance. Since there is no output schema, this field-by-field description is essential and complete.

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 has zero parameters, and the description explicitly states 'Takes no parameters,' which aligns with the empty input schema. Since there are no parameters to explain, the baseline score is 4, and the description adds no further parameter detail needed.

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 'Explain harden's vSphere STIG integration and route continuous enforcement,' which is a specific verb (explain) and resource (STIG integration). It further distinguishes itself from the sibling tool list_stig_controls by stating 'use list_stig_controls to see the actual controls,' clarifying the different purposes.

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?

Explicit usage guidance is provided: 'Call this before assuming a compliance endpoint exists; use list_stig_controls to see the actual controls.' It also explains when to use VCF Operations SPM/ACC UI for fleet-wide enforcement versus harden as the API-scriptable scanner, giving clear conditions and alternatives.

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