enable_feature

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

No annotations provided. Description says 'configures multiple settings at once' but lacks details on reversibility, side effects, or dependencies. For a mutation tool without annotations, this is insufficient.

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?

Two sentences, front-loaded with purpose. Slightly verbose in listing presets but efficient overall. Structure is clear.

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?

Completeness is moderate: lists all presets and references get_settings. Lacks mention of whether enabling is idempotent or if there's a disable counterpart, but given simplicity and no output schema, it is minimally adequate.

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% with a description for 'feature'. Description adds value by listing all presets and aliases, going beyond schema to clarify acceptable values.

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?

Clearly states 'Enable a named feature preset' with verb and resource. Lists all presets and distinguishes from 'get_settings' for viewing, differentiating from sibling tools.

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?

Provides usage context by specifying presets and referencing get_settings for discovery. Does not explicitly state when not to use or mention alternatives, but context is adequate.

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