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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds the returned field set, which is useful, but says nothing about data source, freshness, pagination, or how the sample-vs-real key affects results. With annotations carrying the behavioral load, a 3 is appropriate.

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, front-loaded with the resource and scope, followed by the usage triggers. Every element earns its place, though the field enumeration is slightly list-heavy.

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 read-only list tool, the description covers scope, fields, and usage triggers, and annotations cover the safety profile. Since no output schema exists, naming the returned fields is the right compensating move; only the limit behavior and data source remain unexplained.

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 single 'limit' parameter is fully documented in the schema (including the sample-key cap). The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 resource (Seoul cultural events) with an enumeration of what it covers — exhibitions, concerts, festivals, performances — and lists the fields returned (title, category, district, date, venue, target audience, fee). This makes the tool's scope unmistakable. It doesn't differentiate from siblings, but the seoul_* siblings (air quality, dataset, real estate) don't overlap, so differentiation is largely unnecessary.

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?

Provides concrete trigger phrases — 'cultural events in Seoul' and 'what's on in <Seoul district>' — giving the agent clear context for when to invoke it. There are no exclusions or named alternatives, but no sibling competes for this use case, so the guidance is sufficient.

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