linear_createInitiative

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

The description states 'Create', which implies a non-idempotent mutation, consistent with annotations. However, it does not disclose any additional behavioral traits such as error handling, ownership implications, or default values beyond what annotations already provide.

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 sentence, concise and to the point. It could earn additional value by being more informative, but it contains no unnecessary words.

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?

Given the tool has 8 parameters and a parent output schema, the description is minimally sufficient. However, it lacks context about what an initiative is in Linear's hierarchy, or how it relates to other entities like projects or roadmaps.

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 covers all parameters with descriptions, so baseline is 3. The description adds no additional meaning beyond what the schema already provides. For example, it does not clarify the purpose of fields like 'content' or 'targetDate' in the context of an initiative.

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 the action (Create) and resource (initiative). It is specific enough to distinguish from other create tools like linear_createProject, though it doesn't elaborate on what an initiative is in the context of Linear.

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?

No guidance is provided on when to use this tool versus alternatives like linear_createProject or linear_createRoadmap. The description does not mention prerequisites or context for creating an initiative.

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