get_kr_news_semiconductor

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

Annotations provide readOnlyHint (safe read) and openWorldHint. Description adds useful behavioral context: 5-min cache, payment requirements (x402), and output structure. No contradictions. Some omissions like rate limits or error states, but net positive.

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?

Efficient: two distinct sections (core functionality then payment/docs). Bullet points aid scanning. Could trim payment details into a note, but overall compact and 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 output schema exists, return info in description is supplementary, not required. Caching, payment, and source details covered. No output schema details needed. Minor gaps (no error handling) but adequate for complexity.

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 covers the single parameter 'limit' fully (description, min, max, default). Description adds no new info beyond that. Baseline 3 is appropriate given 100% schema coverage.

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?

Clear verb+resource: 'get' 'Korean semiconductor industry news', specifies aggregation source (Naver), translation, and covered topics (Samsung, SK Hynix, etc.). Distinguished from siblings like get_kr_news_kpop and get_kr_news_semiconductor_summary by explicit domain and output detail.

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?

Implied usage via mention of 'global semiconductor supply-chain signals', but no explicit when-to-use vs. siblings (e.g., summary vs. full news). No exclusions or alternatives given.

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