Execute any KIT API operation

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

With no annotations provided, the description fully discloses that calls are REAL, write operations take effect immediately, and there is no sandbox. It also reveals the validation behavior and how to skip it, which is essential safety-critical information for an escape-hatch tool.

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?

Three sentences with no filler. The first sentence states purpose, the second warns about real side effects, and the third gives the workflow and validation behavior. Each sentence adds unique valuable information.

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 generic API caller with no output schema, the description covers purpose, risks, workflow, and parameter behavior. It references the exact operations to pair with (search_operations, get_operation_schema) and explains validation, making it self-sufficient for an agent.

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 parameters like operation_id, body, query, validate, and path_params are already documented. The description adds meaningful context by directing users to get_operation_schema for body shape and explaining the validate flag's purpose, going beyond the raw 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 states it is an escape hatch that executes ANY of the 160 KIT API operations by operationId, explicitly distinguishing itself from dedicated sibling tools. The verb 'executes' and resource 'KIT API operations' make the tool's purpose unambiguous.

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 explicitly says this tool covers operations without a dedicated tool, establishing when to use it over siblings. The workflow search_operations -> get_operation_schema -> kit_request provides clear step-by-step guidance, and the warning about real calls adds context for cautious usage.

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