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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutating-but-non-destructive profile is covered. Beyond that the description adds nothing: it does not say what happens if the key already exists, whether creation auto-links to a work item, or whether the new concept is scoped to a project.

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 single sentence is front-loaded and free of padding, but its brevity here reflects under-specification rather than economy. There is no structure to speak of because there is only one trivial clause.

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 is a 5-parameter mutation tool with 3 required fields, a 25-value type enum, and no output schema, yet the description never explains the domain model or the effect of creation. An agent must guess the semantics of concept types, standards, and work_item_id from the enum values alone.

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 description coverage is 100%, so every parameter already carries an inline description and the baseline of 3 applies. The description adds no meaning beyond the schema, notably nothing about 'key' uniqueness or how work_item_id and standards affect creation.

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 'Create a concept.' essentially restates the tool name and title without adding information. It never defines what a concept is in this system, nor does it distinguish this tool from siblings like update_concept or add_concept_to_work_item.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g. the project or graph the concept lands in), and no routing to alternatives such as update_concept for existing concepts or add_concept_to_work_item for linking. Usage must be inferred entirely from the name.

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