dw_field_types

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

No annotations; description states it fetches from AddIn registry (not hardcoded) but lacks details on read-only nature, error handling, or performance. Adequate but could add more behavioral context.

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?

Three sentences without waste: purpose, data source, output usage. Front-loaded and efficient.

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?

Explains output format and how to use it, which is sufficient for a simple list tool. Lacks mention of whether data is cached or always live. Reasonably complete given no output schema.

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?

No parameters; schema coverage is 100% (trivially). Description adds no extra param info but doesn't need to. Baseline for zero parameters is appropriate.

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 it lists field editor types from the DW AddIn registry, and mentions output format. Implicitly differentiates from sibling tools like dw_product_field_type_list by specifying usage in dw_field_save and dw_itemtype_create, but does not explicitly contrast.

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 tells when to use: before using field types in dw_field_save or dw_itemtype_create. Does not provide 'when not to use' or alternatives, but context is clear.

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