fgui_add_transition_item

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic add action and does not disclose preconditions (e.g., a document must be open and the target transition must already exist), whether the change is destructive or reversible, or whether a save is required afterward. It is not misleading, but it is far too thin for a mutation tool.

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 single sentence is front-loaded with the verb and contains no wasted words. However, the brevity is closer to under-specification than disciplined conciseness, since the sentence omits the usage, precondition, and parameter context the tool needs.

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?

This is a complex mutation tool with a large schema (14+ $defs, polymorphic value types) and zero annotations, yet the description is one sentence. It does not explain item types, how 'value' varies by 'type', or preconditions. The output schema covers return values, but the missing behavioral and semantic context makes the description inadequate for reliable invocation.

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%, so the description must compensate, but it only hints at the 'item' parameter via '类型化关键帧轨道项' and says nothing about the 'name' parameter. The TransitionItem's polymorphic 'type' and 'value' fields, whose shape varies across 13 possible value types, are entirely unexplained, leaving the agent to guess at valid combinations.

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 states a specific verb (添加/add), a resource (Transition), and an object (类型化关键帧轨道项/typed keyframe track item), which distinguishes it from siblings like fgui_update_transition_item and fgui_remove_transition_item by the add-vs-update/remove verb. However, the term 'typed keyframe track item' is unexplained jargon, leaving some ambiguity about what exactly is being added.

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?

The description gives zero guidance on when to use this tool versus its close siblings fgui_upsert_transition, fgui_update_transition_item, and fgui_remove_transition_item. An agent cannot tell whether this tool requires an existing transition, whether it can create one, or when 'add' is preferred over 'upsert' or 'update'.

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