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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the bar is lower. The description adds useful behavioral context beyond annotations: the result is ordered newest first, includes publish dates and summaries, and content varies by language site. This exceeds the annotation baseline without contradicting it.

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 carry the core behavior, ordering, topics, reading follow-up, and language condition. Every clause earns its place, and the most important scoping information is front-loaded.

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 a single optional parameter, a detailed schema, and an output schema, the description provides everything an agent needs to call the tool correctly: scope, ordering, content shape, language behavior, and a pointer to get_page for reading a full article.

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 description coverage is 100%, and the language parameter is already documented in detail including defaults and site mapping. The description adds a brief mention of language but does not materially go beyond the schema, so the baseline of 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?

States a specific verb and resource: lists Insights articles, enumerates the topic areas, and specifies that results include publish dates and summaries ordered newest first. This clearly distinguishes it from siblings like list_case_studies, list_erp_partners, get_page, and search_site.

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 routes follow-up reading to get_page and gives a conditional usage rule for language selection (English default; set language for Spanish, Portuguese, or Chinese). It does not state exclusions relative to list_case_studies or list_erp_partners, but those distinctions are reasonably inferable from the tool names and the clear article scope.

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