vibemap_create_feature

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

Annotations indicate readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description consistently says 'Create' but adds no extra behavioral context (e.g., whether duplicate names are allowed, required permissions, return value). With annotations already present, the description adds minimal transparency beyond stating the action.

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 the verb and resource. The first sentence declares the core action, and the second adds targeted usage context. No superfluous words or repetition.

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?

The tool has 8 parameters, no output schema, and a meaningful sibling set. The description only states creation and a narrow use case, omitting details about the feature entity, relationships to other VibeMap constructs, or how parameters affect behavior. The description is insufficient for an agent to use the tool confidently without additional knowledge.

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 has 0% description coverage for parameters, and the description does not explain any parameter meaning, defaults, or required fields. Despite 8 parameters including enums and a required projectId and name, the description offers no guidance, forcing the agent to infer from names alone.

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 'Create a new feature in a VibeMap project' with a specific verb and resource. It distinguishes from sibling tools like list_features and update_feature by providing context: 'Use this when reverse-engineering a codebase to register discovered capabilities.'

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 gives a specific use case ('when reverse-engineering a codebase to register discovered capabilities'), which helps the agent decide when to invoke this tool. While it doesn't explicitly state when not to use it or list alternatives, the context is clear and largely sufficient among the siblings.

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