wisdom_get_transform

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

There are no annotations and no output schema, so the description carries the full behavioral burden. 'Get' suggests a read operation, but the description does not disclose error behavior for missing/invalid UUIDs, whether authentication is required, or what the response contains beyond the specification itself.

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 7-word sentence with no filler and the key information front-loaded. It is appropriately sized for a simple one-parameter getter, though it is also minimal enough to feel slightly under-specified.

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 low-complexity tool with one required parameter, the description is nearly complete: the agent knows the action and the key. However, with no output schema and no mention of failure semantics or relationship to sibling transform tools, there is a minor but real completeness gap.

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 single parameter 'uuid' is fully covered in the schema with description 'Transform UUID', so the schema does the heavy lifting. The description adds only 'by UUID', which adds no meaningful semantics beyond what the schema already provides.

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 specific verb ('Get'), a clear resource ('transform specification'), and the lookup mechanism ('by UUID'). This distinguishes it from sibling listing tools such as wisdom_list_transforms, though it doesn't explicitly name alternatives.

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 implies use when the agent has a UUID and needs a single transform specification, but it gives no explicit when-to-use guidance and no comparison against alternatives like wisdom_list_transforms or wisdom_get_fragment. The agent must infer the appropriate context.

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