hijack_change_monitor

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

With no annotations, the description carries the full burden of behavioral disclosure. It transparently explains the tool's stateful behavior: on first run it returns a JSON baseline, and on subsequent runs it diffs to detect added, removed, or changed records. This goes beyond basic purpose disclosure, though it does not address potential errors or edge cases like invalid baseline input.

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 description is two concise sentences, front-loaded with the primary purpose and followed by the operational modes. Every clause adds value, with no filler or repetition of schema details.

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 complete enough for a 2-parameter tool with no output schema. It explains the two distinct invocation scenarios and what output to expect (JSON baseline vs. diff). It could add more detail about error conditions or the exact diff format, but that is not essential for correct invocation.

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% with both parameters defined, but the description adds behavioral meaning beyond the schema. It clarifies that 'baseline' is a JSON string from a prior run and explains the consequence of omitting it (returns the current state as the initial baseline). This effectively compensates for any ambiguity in the raw 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 clearly states the tool's purpose: 'Monitor DNS record changes by comparing current records against a stored baseline.' It uses specific verbs (monitor, compare) and identifies the resource (DNS records), distinguishing it from sibling tools like hijack_dangling_cname that focus on specific vulnerability types.

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 explains the two usage modes: first run (returns initial baseline) and subsequent runs (diffs against provided baseline). This provides clear context on how to invoke the tool correctly. However, it does not explicitly mention when not to use it or name alternative tools, so it falls short of a 5.

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