get_scene_group_plan

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It adds '免费' (free) and implies a read-only query through '查', but it does not explicitly state whether the operation is non-destructive, what the response contains, whether results can be empty, or any rate/access considerations. The transparency is minimal.

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 description is extremely compact: a clear action, a resource with explanation, and a cost note. Every part earns its place, and no redundant wording exists.

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 simple one-parameter getter, the description covers the core purpose and input context. Yet with no output schema, it does not describe what the tool returns, how to interpret the scene group plan, or how the result differs from other planning artifacts. It is adequate but not complete for an agent that must consume the result.

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. It partially does by mentioning '某一集', which maps to the single episode_id parameter. However, it does not add detail beyond what the schema already provides via the parameter name and integer type, such as how to obtain valid episode IDs or what edge cases exist.

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 '查' (query), a clear resource ('某一集的场景组规划'), and adds a parenthetical explaining what scene group planning means ('镜头如何归组做连续长镜'). This distinguishes it from sibling generation tools like generate_scene_groups.

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 no guidance on when to use this tool versus alternatives such as generate_scene_groups or other getters. It implies usage through '查' but does not state when it should be preferred, what conditions make it relevant, or when another tool would be more appropriate.

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