create_knowledge_article

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

Annotations already indicate readOnlyHint=false, so the mutation nature is known. The description adds the WRITE_ENABLED prerequisite. No additional behavioral details like side effects, return value, or error conditions are provided, but given annotations, the description adds moderate value.

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 a single, non-redundant sentence that efficiently communicates the tool's purpose and a key prerequisite. No wasted words.

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?

The description covers the core purpose and a constraint, but lacks information on the expected behavior (e.g., whether the article is created as draft or published, whether it triggers workflows, or what the response contains). The schema compensates partially, but the tool's complexity suggests more context would benefit 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% with clear descriptions for all 4 parameters. The description adds no further parameter meaning, so default baseline score of 3 applies.

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 'Create a new knowledge article' which is a specific verb+resource combination. It distinguishes from sibling tools like update_knowledge_article and publish_knowledge_article by the action 'create' and the resource 'knowledge article'.

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 includes a prerequisite condition 'requires WRITE_ENABLED=true', which provides basic usage guidance. However, it does not compare with alternatives, state when to use vs. not use, or provide context on expected outcomes.

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