clear_programmer

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

No annotations are provided, so the description must fully disclose behavioral traits. However, it only says 'Clear the programmer' without explaining what 'clear' entails (e.g., resets values, deletes data, irreversible). The behavioral impact is unclear, which is especially concerning for a destructive operation.

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 very concise: a single sentence for the action, followed by clear parameter documentation and examples. No unnecessary wording. However, the core description could benefit from slightly more context without becoming verbose.

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 tool's simplicity (one parameter) and the existence of an output schema, the description is adequate but leaves gaps. It does not explain the nature of the return value or the broader implications of clearing the programmer (e.g., whether it affects other parts of the system).

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 schema provides the 'mode' parameter with a default but no enum or description. The description compensates by listing four specific values ('all', 'selection', 'active', 'default') and giving examples. This adds significant meaning beyond the schema's bare definition.

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 action ('Clear the programmer') and provides specific modes ('all', 'selection', 'active', 'default') that define the scope. This verb+resource combination is distinct from sibling tools, as no other sibling explicitly deals with clearing the programmer.

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 does not provide guidance on when to use this tool versus alternatives. It lists modes but does not explain when each mode is appropriate or what the implications are. No exclusions or prerequisites are mentioned.

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