create_supershift_shifts

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

The description discloses the default dry-run behavior, which is important. However, it omits other behavioral traits such as the effect of setting dry_run to false, error conditions, or idempotency. Without annotations, the description carries the full burden and 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?

The description is extremely concise—two sentences with no wasted words. The first sentence clearly states the action, and the second adds critical default behavior. It is well-structured for immediate comprehension.

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?

Despite having an output schema, the description fails to provide enough context for an agent to use the tool correctly. Key details about parameter formats, backend options, and behavior when dry_run is false are missing. Given the complexity and numerous siblings, the description is incomplete.

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 0%, so the description must explain parameters. It does not explain the 'shifts' array structure, the meaning of 'backend', 'dry_run', or 'profile_path'. This leaves the agent with no guidance on how to populate these parameters.

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 tool creates shifts, which is the primary purpose. However, it does not distinguish this from sibling tools like create_supershift_shifts_from_text or create_supershift_sqlite_shifts, which also create shifts but through different means.

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 its siblings. The mention of 'configured backend' is vague and does not help an agent decide between alternatives.

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