Execute any KIT API operation

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

With no annotations provided, the description carries the full burden, and it excels: it warns that calls are REAL, write operations take effect immediately, there is no sandbox, and the request body is validated before sending unless validate=false. These are exactly the behavioral facts an agent needs to make safe decisions.

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?

Four tight sentences front-load the critical warning and then give the workflow in a compact sequence. Every sentence adds operational value with no filler or repetition.

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 high-complexity generic tool with no output schema, the description covers safety, workflow, validation behavior, and the relationship to sibling tools. Nothing essential is missing for an agent to select and invoke it correctly.

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%, so the schema already documents all parameters. The description adds meaningful guidance by directing agents to get_operation_schema for the exact body shape and by clarifying that validation can be disabled via validate=false, which enriches the parameter semantics beyond the bare schema.

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 identifies this as a generic escape hatch that executes any of 168 KIT API operations by operationId, explicitly including operations without a dedicated tool. This distinguishes it sharply from the many sibling tools that wrap individual operations.

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?

It provides an explicit workflow — search_operations, then get_operation_schema, then kit_request — and positions the tool as the path for operations lacking a dedicated sibling tool. It also tells agents when validation can be skipped, leaving little ambiguity about how to invoke it correctly.

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