clear_context_scripts

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

The description discloses key behaviors: clearing all categories when category is None, and the effect of clear_permanent on temporary vs permanent scripts. No annotations exist, so this is sufficient for transparency, though it could mention reversibility.

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 short (4 sentences) and structured with purpose, Args, and Returns. Every sentence adds value, and the purpose is front-loaded.

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?

The description explains the core functionality and parameter behavior, but lacks details on the return value ('Confirmation message' is vague) and potential side effects (e.g., impact on running scripts).

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?

With 0% schema coverage, the description adds meaning by explaining each parameter's role and constraints (e.g., script_name requires category) beyond the schema's field names and types.

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 context scripts from the registry' uses a specific verb ('clear') and resource ('context scripts from the registry'), distinguishing it from siblings like 'clear_shared_context' which clears shared context.

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 explains parameter behavior (e.g., 'script_name requires category to be specified') but does not explicitly state when to use this tool over alternatives like 'clear_shared_context' or when not to use it.

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