create_devto_article

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

Without annotations, the description discloses creation of draft vs published, authentication method, and default safety. Does not mention rate limits or idempotency but covers major behavioral traits.

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?

Well-structured with a lead sentence, parameter list, and return description. Each sentence adds value, though slightly verbose for the number of parameters.

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 10 parameters and an output schema, the description covers all inputs, behavior, and return. Missing error handling details but adequate for standard usage.

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?

Despite 0% schema description coverage, the tool description explains every parameter (title, body_markdown, published, tags, etc.) with sufficient detail, adding meaning beyond the bare 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 states 'Create a dev.to article or draft using the authenticated DEV API.' This clearly identifies the verb (create), resource (article/draft), and distinguishes from sibling tools (search, get, update).

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?

Provides clear context: 'using the authenticated DEV API,' default published=false for safety, and fallback to environment variable for API key. No explicit when-not-to-use, but sufficient guidance for typical usage.

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