createDataType

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

The description reveals that the system does NOT enforce uniqueness on category_name, leading to potential corruption. It details the required pre-check and consequences of duplicates. This adds significant behavioral context beyond the annotations.

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 well-structured with clear sections (Use when, Required, Pre-check, Enums, See also). It is slightly verbose but every sentence provides value. Front-loaded with purpose.

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?

Despite no output schema, the description fully covers input parameters, behavioral requirements (duplicate checking), and edge cases (reuse, ask, alternate name). References sibling tool updateDataType. Complete for agent decision-making.

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%, but the description adds meaning: it lists required parameters, explains enum values for category_active and limit_available, and provides pre-check context that enhances parameter understanding.

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 action: 'Create a data type - Define a new content-type template.' It specifies that this is for new post types and that most sites are pre-configured, distinguishing it from related tools like updateDataType.

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: 'Only do this when the user explicitly wants a new post type.' Provides a pre-check to avoid duplicates, with clear steps and alternatives (reuse via updateDataType, ask user, pick alternate name). Includes when-not-to-use guidance.

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