generate_mdf_import_template

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

With no annotations, the description carries full burden for behavioral disclosure. It explains the output (CSV template with fields and comments) but fails to mention authentication requirements (params include auth_user_id and auth_password), the role of data_center, or any side effects. The template generation is non-destructive, but this is implied.

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 concise (two sentences) and front-loads the main purpose. It is efficient but could be improved by including parameter context. The structure is logical and easy to parse.

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?

While the output schema exists (reducing need for return value explanation), the description omits key parameter details (data_center, auth) and does not differentiate from very similar sibling tools like 'generate_import_template'. The tool's complexity (5 params, 1 required) warrants more completeness.

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 only 40%, meaning 3 of 5 parameters lack schema descriptions. The tool description adds no extra meaning for these undocumented parameters (data_center, auth_user_id, auth_password). It does not clarify their usage or format, failing to compensate for the low 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 states the tool generates an import template for an MDF object, specifically a CSV-ready template with key fields, required fields, and optional editable fields with field type comments. This distinguishes it from sibling tools like 'generate_import_template' which may be for different object 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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'generate_import_template' for non-MDF objects) or prerequisites like authentication or data center configuration. The description implies usage for MDF object import template generation but lacks explicit context.

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