feishu_create_event

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

No annotations are provided, so the description carries the full behavioral burden. It mentions the required inputs but says nothing about side effects (whether attendees are invited/notified), auth/permission needs, or what the call returns. For a mutation tool with zero annotation coverage and 11 parameters, this is a significant gap.

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?

Three tight sentences: purpose, trigger phrases, required inputs, in that order. Every sentence earns its place, though the required-inputs sentence is largely redundant given the schema's required list.

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?

No output schema exists and no annotations, so the description is the only behavioral signal. It adequately covers purpose and trigger conditions but omits side effects and return behavior, leaving the mutation semantics under-specified for an 11-parameter 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 100% with bilingual descriptions on every property, so the schema already documents parameters fully. The description only restates the four required inputs (calendar ID, title, start/end time) and adds no syntax or format detail beyond the schema, 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 verb and resource ('创建飞书日程/会议' – create a Feishu calendar event/meeting), which is unambiguous. It does not explicitly contrast with siblings like feishu_update_event or feishu_create_calendar, but the verb 'create' plus 'event' cleanly separates it from the update/delete/get tools.

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 utterances ('创建日程', '新建会议', '安排会议', '添加日程', '预约') that map user phrasing directly to this tool, which is strong context. It stops short of naming when NOT to use it or pointing to the sibling for updating/moving an existing event, so it is clear context without exclusions.

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