kci_search_articles

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

No annotations provided, so the description carries full burden. It only states 'retrieves basic information' without disclosing traits like pagination, rate limits, or read-only nature. The presence of 'displayCount' parameter implies pagination, but not explained.

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?

Single sentence that effectively communicates the tool's purpose and scope. No unnecessary words, front-loaded with action verb and target resource.

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?

Adequate but incomplete: describes general functionality but lacks details on output format, pagination behavior, or handling of large result sets. For a search tool with 18 parameters, more contextual framing would help.

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 coverage is 100%, so baseline is 3. The description mentions key parameters (title, author, journal) but adds no new semantics beyond the schema definitions. No enrichment of meaning.

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 function: searching KCI-registered articles by various fields (title, author, journal) and retrieving basic info. It implies a search-and-list capability, distinguishing it from sibling tools like kci_get_article_detail which likely provides full details on a single article.

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?

No explicit guidance on when to use this tool versus alternatives. The description is generic and does not specify use cases, prerequisites, or exclusions, leaving the agent to infer context from sibling names.

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