scroll_clear

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

No annotations are provided, so the description carries full burden for behavioral disclosure. The description only states '清除滚动上下文' (Clear scroll context) without explaining what 'clear' means operationally—whether it's destructive, what permissions are needed, what happens to associated resources, or what the response looks like. For a tool with zero annotation coverage, this is completely inadequate.

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 appropriately concise with a brief purpose statement followed by parameter listings. However, the structure could be improved by front-loading more critical information about the tool's behavior rather than just listing parameters. No wasted sentences, but under-specified.

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 the complexity (a clear/delete operation with 2 parameters), no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It lacks essential context about what 'scroll context' is, how clearing affects system state, error conditions, and relationship to sibling tools. The minimal parameter info doesn't compensate for these gaps.

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?

The description lists parameters 'scroll_id' and 'all' with brief Chinese explanations, but schema description coverage is 0%, so the schema provides no additional documentation. The description adds basic meaning (scroll ID and whether to clear all), but doesn't explain parameter interactions, default behaviors, or format requirements. This partially compensates for the schema gap but remains minimal.

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 '清除滚动上下文' (Clear scroll context) is essentially a tautology that restates the tool name 'scroll_clear' in Chinese. It doesn't specify what 'scroll context' refers to, what resource it operates on, or how it differs from related tools like 'scroll_start' or 'scroll_next' in the sibling list. The purpose is vague and lacks specific verb+resource differentiation.

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 is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, when-not scenarios, or related tools like 'scroll_start' or 'scroll_next' from the sibling list. This leaves the agent with no context for appropriate tool selection.

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