Read one public Wikivibe article by absolute URL, path, or section plus slug.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Absolute article URL or localized path. | |
| path | No | Article path, for example /ru/novosti/example/. | |
| slug | No | Article slug when url/path is not provided. | |
| locale | No | ru | |
| section | No | Section slug when url/path is not provided. | |
| maxChars | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Describes as 'Read' and 'public' but no annotation support. Missing details on auth, error handling, or response format beyond maxChars limit.
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, no fluff, front-loads key information. Efficient.
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?
Covers main identification methods and maxChars. Lacks output description and error handling, but sufficient for read operation with no output schema.
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?
Description clarifies conditional logic (url OR path OR section+slug) not explicit in schema. Schema covers most params; locale and maxChars have defaults. Adds value beyond 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?
Clear verb 'Read' and resource 'article' with multiple identification methods (URL, path, section+slug). Distinguishes from sibling search/list tools.
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?
Implied usage: when you have a way to identify a specific article. No explicit when-to-use or when-not-to-use compared to search_articles or list_latest_articles.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource and action: get for single items, list for collections, search for finding, and recommend for project-based suggestions. No two tools have overlapping purposes.
All tool names follow a consistent verb_noun snake_case pattern (e.g., get_article, search_skills). The verbs and nouns are clearly descriptive and uniform across the set.
With 9 tools, the set is well-scoped for a public knowledge server covering articles, design templates, and AI skills. Each tool serves a clear role without redundancy or overload.
The tool set provides comprehensive read and search operations for all three content types, plus a recommendation feature. Minor gaps exist, such as no listing of all articles by section or pagination support, but core workflows are covered.
