devto_create_article

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

With no annotations, the description carries the full behavioral disclosure burden. It excellently surfaces the two most important behaviors: articles are drafts by default, and passing `published: true` triggers a real, immediate, public action. It does not mention response details or edge-case behaviors, but the key side-effect risk is transparently disclosed.

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?

Two sentences deliver exactly the essential information with no filler. The primary action is stated first, followed by the critical default-behavior warning. Every word earns its place.

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 create operation with nine parameters, the rich schema descriptions and the tool description together provide enough context to invoke the tool correctly. The description does not cover the response format, but with no output schema present this is a modest gap rather than a blocking one.

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 100%, so the schema already documents all nine parameters well. The description adds meaningful emphasis around the `published` parameter's default and side effects, but it does not materially extend the semantic information already present in the schema.

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 opens with 'Create an article,' a specific verb and resource pair, and then sharpens the scope with a critical default: it creates a DRAFT unless `published: true` is passed. This clearly differentiates it from publication-oriented siblings and leaves no ambiguity about what the tool does.

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 gives clear context that this tool creates articles and that publishing should be an explicit decision, but it does not explicitly state when to prefer this tool over alternatives like `devto_update_article` or `devto_publish_article`. The usage guidance is implied rather than spelled out.

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