wisdom_create_transform

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

There are no annotations, so the description carries the full burden of behavioral disclosure, and it only says 'Create a new transform specification.' It does not disclose that this is a persistent write operation, what identifiers or values it returns, whether duplicate names are rejected, or what validation is applied to transform_to/transform_from values. For a mutation tool with zero annotation coverage, this is a material gap.

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 five-word sentence with no redundancy, so there is nothing to cut. However, its brevity borders on under-specification: for a 6-parameter creation tool it carries no usage, prerequisite, or behavioral context, so the economy is not earned by density of 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?

With no annotations and no output schema, the description is the only behavioral contract, and one sentence is insufficient for a creation tool with 6 parameters. The agent cannot learn what the call returns, whether side effects are reversible, or how this relates to the five other transform-related siblings. The schema covers parameters, but everything around invoking the tool correctly is missing.

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%, so every parameter is documented in the schema itself, including examples for transform_to ('text/markdown') and transform_from ('text/plain'). The description adds no parameter-level meaning beyond the schema, which sets the baseline at 3. additional_data ('Additional configuration (JSON)') is the vaguest parameter, but the description does nothing to clarify its expected structure.

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 states a clear action ('Create') and resource ('transform specification'), which is a complete verb+object construction. However, it never explains what a transform specification actually is (a reusable mapping from a source format like text/plain to a target format like text/markdown), so an agent must infer this from the schema. It also doesn't explicitly distinguish creation from the sibling transform-execution tools like wisdom_transform_to_fragment or wisdom_auto_transform, though the word 'specification' offers a hint.

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?

No guidance is given about when to create a transform versus using alternatives like wisdom_auto_transform, wisdom_transform_to_fragment, or wisdom_store_transformed_fragments, all of which are siblings. No prerequisites are mentioned — for instance, whether a project must be set (wisdom_set_project) or whether the tags parameter requires pre-existing tag UUIDs. The agent is left to guess when this tool is the right choice.

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