Set DAT content (whole)

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

Annotations already indicate destructiveHint=true. Description adds safety behavior: 'Refuses to write empty/whitespace-only text unless confirm_wipe:true is passed, preventing silent data loss.' This goes beyond annotations and provides crucial behavioral insight.

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?

Two concise sentences with no fluff. Front-loaded with action and resource, then provides contrast and safety note. Every word earns its place.

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?

Given the tool's moderate complexity (3 params, no output schema, no nested objects), the description covers purpose, usage, constraints, and safety. It is complete for an agent to decide when and how to invoke.

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 covers 100% of parameters with descriptions. The description implicitly references 'confirm_wipe:true' but does not add substantial new meaning beyond the schema. Meets baseline for high schema coverage.

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 specifies the verb 'Overwrite' and the resource 'Text or Table DAT's entire .text'. It distinguishes itself from sibling tool 'edit_dat_content' by contrasting surgical find-and-replace vs full replacement.

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?

Explicitly states when to use: 'to deploy a full script or template'. Also provides clear alternative: 'Unlike edit_dat_content (which makes a surgical find-and-replace)'. Additionally, warns about refusal to write empty text and the need for confirm_wipe parameter.

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