search_articles

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

Without annotations, describes that it returns a set of summary fields and directs to get_article for full content. Discloses the specific fields returned, but lacks details on pagination, ordering, or case sensitivity.

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?

Two sentences, no wasted words. First sentence states purpose and return fields, second gives sibling guidance. Efficient and well-structured.

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 3 optional parameters and no output schema, the description adequately covers what the tool does and what it returns. Could mention default state or pagination, but not essential for a search tool.

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 has 100% coverage with descriptions for each parameter. Description adds no extra meaning beyond the schema; it only mentions 'using keywords' which aligns with the 'phrase' parameter.

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?

Clearly states 'search for Intercom Help Center articles using keywords', specifying verb and resource. Distinguishes from siblings like list_articles and get_article by emphasizing keyword-based search and listing return fields.

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?

Explicitly tells when to use get_article for full content, providing a clear alternative. Implies search_articles is for summaries and keyword-based lookup, but does not say when not to use it (e.g., if no keywords).

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