feishu_get_event_list

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

No annotations are provided, so the description carries the full burden. It mentions the action and a required input, but fails to disclose pagination behavior (despite page_size/page_token params), rate limits, sorting order, or what happens if no events exist. It does not describe what the returned list contains, which matters because there is no output schema.

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?

Efficient, two-sentence description with the core purpose first, then trigger phrases. No wasted words. Could be slightly more concise on trigger examples, but they add value for intent matching.

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 list-fetching tool with 5 parameters (including pagination), no output schema, and no annotations, the description is insufficient. It omits pagination guidance, return shape, time-range filtering behavior, and default values. An agent cannot fully anticipate behavior from this description alone.

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%, so baseline is 3. The description only adds that calendar_id is required, which is already indicated by the required field in the schema. No additional meaning is provided beyond the 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?

Clear verb+resource: querying a Feishu calendar/event list. It's a list-fetching tool, distinguishable from feishu_get_event (single event) and feishu_get_calendar_list by the 'calendar ID' requirement. However, it doesn't explicitly name the sibling tools it contrasts with, preventing a full 5.

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 natural-language trigger phrases (查看日程, 今天的安排, etc.) which give clear usage context. It states the prerequisite of providing a calendar ID. However, it doesn't state when NOT to use this (e.g., vs get_event for a single event) or explicitly cross-reference alternatives.

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