create_transformation_project

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

The description notes it is a write operation and requires user confirmation, but with no annotations provided, it lacks details on permissions, side effects, or what happens on success/failure. This is adequate but not thorough.

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 with two sentences, each serving a clear purpose: the warning and the action. No unnecessary words.

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 tool is simple with two parameters and no output schema, but the description does not mention return values or error conditions. For a write operation, this is a gap, though the schema and warning cover basic needs.

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?

The input schema covers both parameters with descriptions, so the description adds little beyond the schema. It does instruct to read a schema file first, which is a behavioral hint but not parameter semantics. 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 clearly states it creates a new transformation project, using a specific verb and resource. However, it does not explicitly distinguish from sibling tools like 'create_transformation' or 'modify_transformation_project', though the name itself is specific.

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 includes a warning to confirm with the user before calling, which provides basic usage guidance. However, it does not specify when to use this tool versus alternatives or provide context on prerequisites or exclusions.

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