Record a network mutation

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

No annotations provided, so description must carry behavioral disclosure. It explains the core behavior (logging with optional compensator) but omits details like auth requirements, side effects, error handling, or what happens after logging.

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?

Single sentence that front-loads the purpose and includes a concrete example. No superfluous words.

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 6 parameters and no output schema, the description covers the core functionality but lacks details on return value, error states, or how logged entries are used later. Adequate but not comprehensive.

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 clear descriptions. The description adds meaning by explaining the optional compensator parameters (Url, Body, Method) and their role in undoing mutations, which goes beyond the schema's basic labels.

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?

Description clearly states the tool logs an HTTP mutation (POST/PUT/PATCH/DELETE) made by the agent, with an optional compensating request for undo. It distinguishes from siblings like walkback_record_reversal by focusing on HTTP mutations and compensating requests.

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?

Description implies usage for logging HTTP mutations when undo capability is needed, but lacks explicit when-to-use or when-not-to-use guidance compared to similar tools like walkback_record_reversal or walkback_log.

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