get_press_articleslug を指定して、検証済みプレス1件の要約(lead)・構造化された統計(facts)・関連求人・帰属(provenance)を取得します（本文は企業自身が投稿したもののみ、運営取込は著作権配慮で原本リンクを提供）。Get one verified press article: summary, structured facts, related jobs, and provenance. Full body is included only for company-submitted articles; for operator-curated ones the original source link is provided instead.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | 記事の slug（search_press の結果に含まれる） |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses that full body is included only for company-submitted articles, and for operator-curated ones the original source link is provided instead. This is key behavioral insight beyond a simple read operation.
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 extremely concise with two bilingual sentences that cover purpose, input, and behavioral caveat. No redundant information; every sentence adds value.
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 tool with one parameter and no output schema, the description adequately explains what is returned (summary, facts, jobs, provenance) and the full body availability condition. No significant gaps.
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 a single required parameter 'slug' described as coming from search_press results. The description adds meaning by explaining the slug identifies the article and that search_press results contain it, exceeding the schema's basic description.
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 one verified press article by slug, returning summary, facts, related jobs, and provenance. It differentiates from sibling tools (list_company_press and search_press) by focusing on single article retrieval.
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 specifies the required slug parameter and explains when full body is available (company-submitted) vs when only a source link is provided (operator-curated). No explicit guidance on when to use vs alternatives, but the single-article context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: one retrieves a single article by slug, one lists all press for a company, and one searches across companies with category filters. No overlap or ambiguity.
All tools follow a consistent verb_noun pattern in snake_case: get_press_article, list_company_press, search_press. The naming is predictable and uniform.
Three tools is slightly on the low side but appropriate for a focused read-only press retrieval server. The scope is narrow enough that each tool earns its place.
The set covers the core operations for retrieving verified press releases: single article, company listing, and search. Missing potential features like category listing or pagination metadata, but the main workflows are supported.