Get one knowledge base article

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds that the output is markdown, which is useful but limited. It does not disclose any behaviors such as error handling, rate limits, or whether metadata is included alongside the body.

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 a single sentence of eight words, succinctly conveying the core output format without unnecessary detail. It is front-loaded and every word earns its place. The brevity is effective for a simple retrieval tool, though it sacrifices explanatory richness.

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 tool's simplicity (one integer parameter, no output schema) and strong annotations, the description is minimally adequate. However, it lacks any connection to sibling search tools and does not clarify what fields beyond the body might be returned. It is functional but leaves gaps in expected behavior.

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?

The schema has one parameter, article_id, with zero description coverage. The tool description does not explain what article_id refers to or how to locate it, leaving the agent to rely solely on the parameter name. Since schema coverage is 0%, the description should compensate, but it fails to provide any meaningful context.

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 identifies that the tool returns the full body of a solution article in markdown, which specifies both the resource and output format. The title explicitly states 'Get one knowledge base article,' reinforcing the action. It is distinguishable from sibling tools like freshdesk_search_knowledge, but the description alone lacks the explicit verb.

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 is given on when to use this tool versus alternatives such as freshdesk_search_knowledge or freshdesk_get_canned_response. There is no mention of prerequisites or how to obtain an article_id. The description does not indicate whether this should be used after searching for an article or for direct retrieval.

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