create_activity

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

No annotations provided, so description carries full burden. It mentions default values (cost=0 means not entered, payment_timing defaults to ON_SITE) but lacks details on authorization, idempotency, or error handling.

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?

Description is well-structured with an Args section and bullet points, front-loaded with purpose. However, it is somewhat lengthy; could be slightly more concise while retaining all necessary info.

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?

Tool has many parameters (14) and an output schema; description covers parameter semantics and default behaviors adequately. Lacks guidance on timezone handling or complex use cases, but sufficient for a creation tool.

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 0%, but description compensates by explaining each parameter with types, format examples (e.g., '09:30'), and meaning (e.g., 'url: 예약·티켓·문서 링크'). Adds significant value beyond schema.

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?

Description clearly states '일자에 활동을 추가한다' (add activity to a day), specifying verb and resource. Differentiated from siblings like update_activity and delete_activity as a create operation.

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?

Description explains required and optional parameters, provides examples, and references get_trip for IDs. However, it does not explicitly state when to use this tool over alternatives like update or delete.

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