devto_list_my_articles

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds valuable context by explaining that the tool defaults to ALL articles, unlike the raw /articles/me endpoint which returns only published articles, preventing an agent from misinterpreting an empty result for drafts-only accounts.

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 short and front-loaded with the core purpose. The second sentence is slightly convoluted but still earns its place by conveying an important behavioral nuance without unnecessary filler.

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 tool is simple with three optional parameters and no output schema, so the description is adequate in some respects. However, it does not describe what each state returns, pagination behavior, or the response shape, which leaves gaps given the lack of annotation and output schema support.

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 schema has 0% description coverage, so the description must compensate. It only touches the 'state' parameter indirectly by mentioning 'ALL', but provides no information about 'page' or 'per_page'. The schema already defines the defaults and enum values, so the description adds minimal semantic value beyond the structured definition.

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 a specific verb and resource ('List your own articles') and distinguishes this tool from potential siblings by limiting scope to the authenticated user's articles. It also clarifies the default behavior, making the purpose 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?

The description provides clear context for when to use the tool: when retrieving the caller's own articles. It does not explicitly mention when not to use it or name alternatives, but the sibling list contains no other article-list tool, so the context is sufficient.

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