create_onboarding_case

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

The annotations already indicate it's a write operation (readOnlyHint=false) and not destructive. The description adds '[Write]' which is redundant and does not disclose additional behavioral traits such as permission requirements, side effects, or what happens during creation. For a write tool with annotations present, this adds minimal value.

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 plus a tag, which is front-loaded and concise. However, it could be slightly more informative without adding verbosity.

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 mentions 'all standard tasks' but does not explain what these tasks are or what the tool returns (no output schema). For a creation tool, it partially sets expectations but lacks completeness.

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 coverage is 100% with all parameters described. The description does not add any meaning beyond the schema, so baseline 3 is appropriate.

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 resource ('employee onboarding case') and distinguishes it from sibling tools like 'create_offboarding_case' by mentioning 'with all standard tasks'. This clearly states what the tool does.

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 provides no guidance on when to use this tool versus alternatives (e.g., when to create an onboarding case vs an incident or offboarding case). No prerequisites or context for use are given.

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