docs

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

Since no annotations are provided, the description must convey behavioral traits such as side effects or mutation risks. It only says 'management' and lists actions, failing to disclose that 'generate' can modify or overwrite files, that 'overwrite' controls this, or any other operational details.

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, efficient sentence that is front-loaded with the core purpose. It avoids unnecessary words, though it may be too brief to cover the tool's complexity.

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?

This multi-action tool with 6 parameters and no output schema needs a richer description explaining each action's purpose, expected return values, and side effects. The current text is a minimal overview and leaves agents to infer crucial operational details.

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 input schema already provides descriptions for 100% of parameters, so the baseline is 3. The description adds no extra meaning to any parameter; it merely recounts the action names already present in the enum.

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 identifies the resource as '.ctx documentation' and lists concrete actions, making the tool's purpose clear. However, it doesn't elaborate on what each action does or how this differs from sibling documentation tools, so it falls short of 5.

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 action list is present, but the description gives no indication of when to use this tool versus alternatives, nor when to select one action over another. The tool's name implies a scope, but there is no explicit context or exclusions.

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