list_festivals

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

Some behavioral details are disclosed, such as including the period of each item and only confirming 'it happens then' if the queried date falls within the period. However, it does not mention read-only nature, error handling, or side effects, leaving gaps in transparency.

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 concise, consisting of two short Korean sentences. It conveys essential functionality and a key parameter rule without unnecessary verbosity, though the structure is a single block rather than organized sections.

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?

The description lacks an output schema and does not specify the return format or fields, which is critical for an agent to parse results. It also omits details about required parameters and potential filters, making the tool incomplete for production use.

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 description explains date_from (default to today if omitted) and how to interpret it relative to event periods, but provides no semantics for cd (the region code) or limit. With schema coverage at 0%, most parameters remain unexplained.

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's function: listing ongoing or upcoming festivals/events in a region. It also specifies the default behavior for date_from, but does not explicitly differentiate from sibling tools such as list_places, leaving some ambiguity about when to prefer this tool.

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?

There is no guidance on when to use this tool compared to its siblings. The description provides parameter behavior but not selection criteria, so an agent may struggle to decide between list_festivals and list_places.

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