va_get_article

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. As a read operation, it doesn't state whether the article is returned fully, whether metadata is included, what happens for missing/expired article IDs, or whether authentication is required. Minimal disclosure beyond stating it fetches a single article.

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?

A single efficient sentence with zero waste. It's appropriately front-loaded with the core purpose stated in the first few words. However, it could arguably be longer to cover the gaps in param/behavior explanation given it's a simple one-liner.

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?

For a simple two-parameter fetch tool with no output schema, the description is minimal but the tool itself is low complexity. The main gap is the undocumented kbId parameter and lack of usage guidance relative to the sibling va_get_articles. Given the low complexity, this is adequate but not comprehensive.

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 description coverage is 0%, so the description must compensate. It mentions 'by ID' for the article (mapping to articleId) but does not explain kbId at all or clarify that both are required identifiers. The description adds minimal meaning beyond what the schema property names imply.

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 uses a specific verb+resource ('Get a single knowledge base article by ID'), clearly stating what it does. It distinguishes from siblings like va_get_articles (plural list) and va_create_article/va_update_article by the 'single... by ID' scope.

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 guidance on when to use this tool versus alternatives. It doesn't mention when to use va_get_articles instead, nor any prerequisites like needing a valid articleId from a prior list operation. The use case is implied but not stated.

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