dw_field_save

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

Reveals automatic handling of RichTextEditor configuration, but with no annotations, the description must disclose more. Missing details on permissions, destructiveness, return values, or error states.

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?

Concise with three short paragraphs; front-loaded with purpose. No redundant information, but structure could be improved with bullet points for parameters.

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?

Lacks details on output, success/failure indication, prerequisites (e.g., item type existence), and overall mutation behavior. For a tool with 7 parameters and no output schema, more context is needed for effective use.

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?

Adds value by explaining isNew's role and hinting at type discovery via dw_field_types. Schema covers 57% of parameters with descriptions; the description supplements moderately but does not cover all parameters comprehensively.

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?

Clearly states the tool adds or updates a field on a DynamicWeb item type, distinguishing between new (isNew: true) and existing fields. Differentiated from siblings like dw_field_delete and dw_field_list, though not explicitly compared.

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 guidance on using isNew flag and recommends dw_field_types for discovering type aliases. Lacks explicit when-to-use or alternatives, such as when to use product field tools or when not to use this tool.

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