describe_stig_content_sync

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), the description discloses meaningful behavioral detail: 'Read-only, local static content — no database, network, or API call.' It also reveals the key invariant that compliance_api_available is 'always false', which is critical for the agent to know before calling.

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?

Although the description is dense, every sentence earns its place: purpose, return field semantics, routing guidance, and behavioral guarantees. The most important usage instruction is front-loaded, and the output field breakdown compensates for the absent output schema.

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 fully documents the return shape and key field meanings. It also covers behavioral aspects, prerequisites, and the relationship to sibling tools. Nothing critical is missing for an agent to decide when and how to call this tool.

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, so the baseline is 4. The description confirms 'Takes no parameters,' which fully covers the parameter dimension.

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 uses a specific verb-resource pair: 'Explain harden's vSphere STIG integration' and clearly states its routing role. It also distinguishes itself from the sibling tool list_stig_controls by noting that callers should use that tool to see actual controls.

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?

The description provides direct guidance: 'Call this before assuming a compliance endpoint exists; use list_stig_controls to see the actual controls.' This explicitly tells the agent when to invoke this tool and names the alternative, making the usage context unambiguous.

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