get_notice_summary

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

No annotations are provided, so the description carries the burden. It discloses that it uses the search API, requires no separate subscription, and returns a defined set of metadata fields. It does not explicitly state side-effect-free behavior or auth requirements, but the read-oriented language and return list give useful context.

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 compact two-sentence statement. It is front-loaded with the action and resource, and each sentence contributes value without redundancy.

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 one-parameter retrieval tool, the description covers the key aspects: what it returns (all metadata fields listed) and the underlying API usage. There is no output schema, but the return description compensates. It could mention that it returns only the summary and not full content, but the tool name and sibling list imply this.

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?

The single parameter notice_id is fully described in the schema with its type and meaning. The tool description only repeats that the summary is fetched 'by noticeId', adding no extra semantic details beyond the schema's high 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?

The description clearly states the tool fetches a single notice summary using notice_id. The verb 'Hae' and resource 'yksittäisen ilmoituksen yhteenveto' distinguish it from sibling tools like get_notice_full and search_notices.

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 indicates it is for retrieving a summary of one notice, and notes it uses the search API without requiring a separate order. However, it does not explicitly compare with alternatives like get_notice_full or specify when to choose one over the other, so guidance is only implied.

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