Enable Temporary Claude Code Directive

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

With no annotations, the description carries full behavioral disclosure burden. It mentions 'context guardrails and scheduled cleanup' but does not detail specifics like effect on existing directives, destructiveness, authentication needs, or rate limits. The description is adequate but not transparent beyond the core function.

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 a single, 25-word sentence that is concise and front-loaded with the core action. It conveys essential information without verbosity, though it could be better structured.

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 complexity (13 parameters, no output schema, no annotations), the description is too brief. It omits parameter meanings, return behavior, and detailed effect of the directive, making it incomplete for an agent to use correctly without additional 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?

Only 8% schema coverage (expiresAt has a description); the description does not explain any of the 13 parameters. Terms like 'context guardrails' and 'cleanup' hint at some parameters but add no concrete meaning. The description fails to compensate for low schema coverage.

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 enables or updates a global temporary directive for using Claude Code, specifying the action (enable/update), resource (directive), and key constraints (expiry, guardrails, cleanup). It distinguishes from sibling tools claude_directive_status (status check) and claude_directive_disable (disable).

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 explicit guidance on when to use this tool versus its siblings (status, disable). It implies the tool is for enabling a temporary directive, but lacks when-not-to-use criteria or alternative scenarios.

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