update_article

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

No annotations are provided, so the description carries the full burden. It only says 'Update', implying a mutation, but does not disclose whether it performs partial updates, whether missing fields are reset, what permissions are required, or what the response looks like. This is a significant transparency gap for a mutation tool.

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 sentence with no unnecessary words, making it concise and well-structured. However, this brevity sacrifices helpful detail, but for what it is, it is clean and to the point.

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?

Given the tool complexity (6 parameters, no annotations, no output schema), the description is severely incomplete. It omits parameter explanations, side effects, usage context, and return values, making it inadequate for an agent to understand the tool's full behavior.

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 input schema has 6 parameters with zero descriptions, and the description does not add any meaning to them. 'Update a Knowledge Base Article' hints that the parameters like name, content, or folder_id are updatable fields, but provides no specific semantics or constraints. With 0% schema coverage, the description fails to compensate.

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 verb 'update' and the resource 'Knowledge Base Article', which distinguishes it from sibling tools like create_article or archive_article. However, it does not elaborate on what aspects of the article can be updated, but the core purpose is unambiguous.

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?

There is no guidance on when to use this tool versus alternatives. The description is a terse statement of what the tool does, but does not mention prerequisites, exclusions, or scenarios where another tool like create_article or archive_article would be preferred.

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