kaiten_create_sd_request

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

No annotations are provided, so the description must carry the disclosure burden. It does surface a non-obvious behavioral trait — the API may return 405 and creation may be restricted to the portal — which is critical for an agent to know. It does not describe success responses or side effects, but the disclosed limitation is material and beyond what the schema reveals.

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?

Two sentences with no filler; the purpose is front-loaded and the caveat is positioned after. Every word earns its place.

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?

For a 4-parameter create tool with a fully documented schema, the main missing contextual element is the success/error response shape (no output schema) and what to do when the portal-only restriction applies. The 405 caveat is a step in the right direction, but the description stops short of telling the agent how to recover or find the required service_id.

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%: title, priority, service_id, and description all have schema-level descriptions. The tool description adds no parameter semantics, so it stays at the baseline for fully-covered schemas.

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 leads with a specific verb and resource — 'Create a new Service Desk request' — which unambiguously distinguishes it from the many sibling sd_* tools (list/get/update/delete). The 405 note is secondary and does not obscure the primary purpose.

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 explicit when-to-use-versus-alternatives guidance; the description relies on the tool name and first sentence to imply its use case. The note that creation may only be available via the Service Desk portal is a useful caveat for deciding whether to attempt the call, but it does not name alternative tools or say when to prefer them.

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