get_knowledge_article

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

Annotations already mark as read-only (readOnlyHint: true) and open-world (openWorldHint: true). Description adds that it retrieves 'full content' and specifies identifier format, providing useful context beyond annotations without contradicting them.

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?

One efficient sentence with no wasted words. Perfectly concise for a simple retrieval tool.

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?

Given the simple single-parameter tool and no output schema, the description fully covers the purpose and input. It could optionally mention that it returns full content fields, but overall it's complete enough.

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?

Single parameter 'number_or_sysid' with clear description in schema. Description adds no extra meaning beyond what the schema already provides (100% coverage), so baseline 3 is appropriate.

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?

Describes a specific verb ('Get') and resource ('knowledge article') with a clear identifier format ('number (KB...) or sys_id'). Clearly distinguishes from siblings like 'search_knowledge' or 'list_knowledge_bases'.

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?

Implies use for retrieving full article content by identifier, but lacks explicit when-to-use or when-not-to-use guidance or comparison with siblings like 'search_knowledge' or 'list_knowledge_bases'.

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