Create Node

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

No annotations provided, so the description carries full burden. It doesn't disclose required permissions, whether fields must match bundle's field definitions, validation behavior, what happens on invalid bundle, or whether the operation is reversible. For a mutation tool with zero annotation coverage, this is a significant gap.

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?

Single concise sentence, front-loaded with the core action. No wasted words, though brevity here comes at the cost of the missing information noted in other dimensions.

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?

For a mutation tool with nested object parameters, 0% schema coverage, and no annotations, the description is far too thin. It doesn't explain field structure, permission requirements, or validation rules. Output schema exists, so return format need not be described, but input semantics and behavioral context are critically missing.

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 description coverage is 0%, so the description must compensate. It only vaguely refers to 'given fields' without explaining that 'fields' is an object of field name/value pairs, what field types are expected, or how bundle names map to content types. The 'bundle' parameter's relationship to Drupal content types is not clarified.

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?

States a specific verb (Create) and resource (node) with scope qualifier 'of the specified bundle', which distinguishes it from create_media, create_term, create_user siblings. However, it doesn't explicitly differentiate from bulk node creation or other content creation tools.

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 on when to use this tool versus alternatives like generate_test_content, create_media, or content_translation_add. The description implies single-node creation but doesn't state when a caller should prefer this over bulk operations or other content types.

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