Generate ContextStream rules

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

Annotations are unhelpful (all false). The description does not explicitly state that the tool writes files to disk, which is implied by the name but not confirmed. It mentions 'dry_run' parameter that returns content without writing, but does not disclose the default behavior of overwriting existing files (overwrite_existing parameter).

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 concise at two sentences, front-loading the main purpose. However, the second sentence includes a long list of editors that is somewhat redundant with the schema, though still acceptable.

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?

With 12 parameters and no output schema, the description lacks details on output format, side effects (file creation/overwrite), and comparison to sibling tools. The tool is relatively complex but the description is too brief to fully inform the agent.

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?

Schema coverage is 100%, so parameter descriptions are already present. The description adds some context (e.g., editor list, default behavior) but lists editors inconsistently (includes opencode, windsurf, antigravity not in enum). This adds marginal value beyond the schema.

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 'Generate AI rule files for editors', and the title adds 'ContextStream rules', making the purpose clear. However, it does not distinguish from the sibling tool 'generate_editor_rules', which likely serves a similar function.

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 provides minimal guidance: 'Defaults to the current project folder; no folder_path required when run from a project.' It does not specify when to use this tool over the similar 'generate_editor_rules', nor does it mention 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.