article_list

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states that it retrieves a list, offering no information about whether it returns only published articles, sorting behavior, pagination defaults, or any side effects. This is minimal but not misleading.

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 extremely short and not verbose, but it lacks substantive information. It is a single generic sentence that could apply to any list endpoint, so while it is concise, it does not 'earn its place' by providing meaningful specifics.

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 has 5 optional filters, no output schema, and multiple closely related sibling tools. The description does not explain the tool's filterable nature, default behavior, or how it differs from 'get_articles'. It is incomplete for effective selection and invocation.

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 descriptions cover all 5 parameters (limit, style, offset, status, language) with clear definitions and enum values, so the description does not need to repeat them. However, the description adds zero value beyond the schema—it doesn't mention how parameters interact or provide any additional context.

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 tool's core function: retrieving a list of articles. However, it does not differentiate from sibling tools like 'get_articles' or 'article_search', so it lacks specificity to distinguish among similar operations.

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 no guidance on when to use this tool versus alternatives. With siblings like 'get_articles', 'article_search', and 'get_web3_news', a user would not know which tool fits their use case, and no exclusions or alternative recommendations are given.

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