Get Knowledge Article

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

The description discloses that it returns full content including HTML body. No annotations are provided, so the description carries the burden. It does not mention any side effects, permissions, or performance, but for a simple read operation it is adequate.

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 two sentences, front-loaded with the main purpose, followed by usage context. Every sentence adds value, and there is no extraneous information.

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 retrieval tool with only two parameters and no output schema, the description is sufficient. It explains what it does and when to use it. It could potentially detail the output structure, but the mention of 'HTML body text' gives some indication.

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% with clear parameter descriptions for 'instance' and 'sys_id'. The description adds no additional parameter information beyond the schema, so baseline score of 3 applies.

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 retrieves the full content of a knowledge article by sys_id, including HTML body. It distinguishes from siblings like list_kb_articles (which only returns summaries) by specifying it gets full content.

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 explicitly says 'use this when you need to read, review, or extract content from an article.' This provides clear context. While it doesn't mention when not to use, the sibling list implies alternatives for creation or listing.

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