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

The description simply states it creates a node, which is already implied by readOnlyHint=false. It does not disclose what happens on success, whether a unique identifier is returned, how existing nodes are affected, or any other behavioral traits beyond the structured 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 very short and front-loaded with the core action. However, the label default sentence is redundant with the schema and does not fully earn its place, though it does not significantly bloat the description.

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 moderate-complexity create operation, the description plus the schema provides enough to invoke the tool, but it lacks any behavioral context or relationship to sibling tools. The output schema covers return values, so that gap is acceptable, but usage guidance is 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?

The description only mentions that 'Label defaults to 'content'', which merely repeats the schema's default value. It adds no meaning about title, text, source, score_boost, or custom_metadata beyond what the schema already documents, and schema coverage is only 67%.

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 uses a specific verb and resource: 'Create a new content node in the knowledge base.' It clearly distinguishes the operation from sibling tools like read_node, update_node, and list_nodes by stating 'new' and 'knowledge base'.

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?

The description does not provide any guidance about when to use this tool versus alternatives like create_prompt or update_node. There is no mention of exclusions, prerequisites, or scenarios that would favor a different sibling tool.

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