check_staging

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

With no annotations provided, the description carries the full burden and discloses the data source (GhostWatch), the operation type (association check), and the return structure (cluster details, confidence score, signal count, AI assessment). It implies this is a read-only lookup but omits operational details like rate limits or latency.

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?

Well front-loaded with the core action in the first sentence. The GhostWatch explanation justifies its existence by defining the specialized threat domain. The Args section is necessary given 0% schema coverage. Every sentence earns its place by adding domain context or parameter documentation.

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?

Appropriately complete for a single-parameter lookup tool. The description adequately covers the threat intelligence domain (GhostWatch pre-attack), input semantics, and output summary, even though an output schema exists to handle detailed return structures.

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 description coverage is 0%, requiring the description to compensate. The 'Args' section successfully documents the 'indicator' parameter as accepting 'IP address or domain' and explains its purpose ('to check for staging activity'), fully compensating for the undocumented schema.

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 action verb ('Check') and clearly defines the resource being queried (GhostWatch pre-attack staging cluster). It explicitly differentiates from generic siblings like check_ip and check_domain by specifying the GhostWatch threat intelligence context and the 'pre-attack staging' domain.

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?

Provides clear context about when this tool is valuable—during the 'quiet window' when attackers stage infrastructure before weaponization. This helps agents distinguish it from generic reputation checks. Lacks explicit 'when not to use' or named alternatives, but the threat context is clearly defined.

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