getArticle

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

With no annotations, the description must carry the burden of behavioral disclosure. 'Get details' implies a read-only operation, but it does not mention potential locale behavior, error cases, or return specifics. It conveys the core behavior but lacks deeper context, which is acceptable for a simple getter but not fully transparent.

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, front-loaded sentence that conveys the essential information without any filler. Every word earns its place.

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 get-by-id tool with full schema documentation, the description is sufficiently complete. It states what the tool does, and the schema covers parameters. The lack of an output schema is not a gap because the description says it returns 'details' and the tool is trivial in scope. It could mention locale behavior, but that is not necessary for basic usability.

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%, so the schema already describes both 'id' and 'locale'. The description adds minimal semantic value beyond repeating 'by ID', which reinforces the 'id' parameter but does not elaborate on 'locale' or provide additional meaning.

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 'Get' and clearly identifies the resource as 'a specific Zendesk Help Center article by ID'. This clearly distinguishes it from the sibling tool 'searchArticles', which is for searching rather than retrieving by ID.

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 phrase 'by ID' clearly indicates this tool is for retrieving a known article, which implies when to use it. However, it does not explicitly mention when not to use it or name the alternative 'searchArticles'. Thus it provides clear context but lacks explicit exclusion.

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