get_material_guidelines

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

No annotations provided, so description carries full burden. It states it's a read operation ('读取') and 'no upload needed', implying no side effects. However, does not disclose auth requirements or return format, leaving some behavioral uncertainty.

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 sentence packs purpose, scope, and usage timing without redundancy. Front-loaded with key action '读取' and ends with pragmatic when-to-call. 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 zero parameters and no output schema, the description tells the agent what it does and when to call. Could mention the return format, but for a read-only guidelines tool, it is adequate and fits the workflow context.

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?

Zero parameters, so baseline 4 per rules. Description adds meaning by explaining what conventions are read (duration, pageMarks, audio), which is useful beyond the empty 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?

The description clearly states the tool reads platform conventions for material duration, pageMarks, and video original sound when embedding HTML. It distinguishes from siblings that perform actions like upload, render, or analyze.

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?

Explicitly says 'should be called before generating HTML/dividing pageMarks', providing clear when-to-use guidance. Lacks explicit exclusions or alternatives, but context with siblings implies this is a preparatory step.

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