create_knowledge_article

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description only adds the WRITE_ENABLED constraint. Other behaviors like return value or post-creation state are not disclosed. For a creation tool, this is insufficient transparency.

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 sentence with essential information (purpose and prerequisite). No wasted words. Perfectly concise.

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 is too brief. It does not mention what the tool returns (e.g., sys_id of the new article), nor does it clarify whether the article is created as draft or published. With siblings like publish_knowledge_article, this context is missing. Incomplete for a creation tool with no output schema.

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%, so baseline is 3. The description adds no parameter-specific information beyond what the schema already provides. The schema's own descriptions are adequate but not enhanced.

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 and resource. It adds a prerequisite (WRITE_ENABLED=true). While it doesn't explicitly distinguish from siblings like update_knowledge_article, the verb 'create' provides inherent distinction.

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?

Only the prerequisite 'requires WRITE_ENABLED=true' is provided. There is no guidance on when to use this tool versus alternatives, no exclusions, and no mention of when not to use it. This is minimal guidance.

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