Create Shortcut Project

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

With no annotations, the description carries the full burden, but it only restates the tool's name. It omits the required confirm=CONFIRM_WRITE behavior, dry_run support, and any side effects or permission requirements, making it nearly as opaque as no description at all.

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, which is concise, but it is severely under-specified for a tool with seven parameters and no annotations. This is not meaningful conciseness; it is absent specification.

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 description is completely inadequate for this tool's complexity. It lacks any information about return values, required fields, team/workspace context, confirmation requirements, or how it relates to other project operations. Without output schema or annotations, the agent has almost no guidance.

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 description provides no parameter information, and schema description coverage is only 29%. Since the description must compensate for the poorly documented schema, the complete absence of parameter semantics is a critical failure.

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 uses a specific verb 'Create' and names the exact resource 'project' in Shortcut. This clearly distinguishes it from sibling tools that create epics, milestones, stories, or other entities.

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 guidance about when to use this tool versus alternatives. It simply states what it does without mentioning prerequisites, exclusions, or comparing with other create tools.

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