memory_get_current_episode

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

The description indicates a read operation, which is consistent with a 'get' verb. No annotations are provided, so the description carries burden. It mentions 'active episode' but does not specify behavior (e.g., what happens if no active episode, whether it returns immediately, or side effects). For a simple read, this is adequate but not detailed.

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?

Single, concise sentence that front-loads the purpose. No wasted words.

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?

Given no parameters, no output schema, and low complexity, the description is mostly complete. However, it could mention what kind of information is returned (e.g., ID, name, status) to fully inform the agent. Still, it is sufficient for a simple getter.

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?

There are zero parameters, and schema coverage is 100%. The description does not need to add parameter info. Baseline 4 is appropriate.

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: getting current active episode info. The name 'memory_get_current_episode' reinforces this. However, it does not differentiate from siblings like memory_get_episode_detail or memory_list_episodes, which could confuse an agent.

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?

No guidance on when to use this tool versus alternatives (e.g., memory_get_episode_detail for specific episode, memory_list_episodes for listing). The agent is left to infer based on name alone.

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