run_transform

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

With no annotations, the description carries the full transparency burden. It does disclose an important behavioral trait: a transform can report success while producing no entities, and it points to further documentation. However, it does not clarify potential side effects, permission requirements, or error/return behavior beyond the schema. The added warning is helpful but not comprehensive.

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 compact and well-organized: a one-sentence purpose, a brief cautionary note, and a clear Args section. Every part serves a purpose, and it is not overly verbose. It could be slightly more concise by merging the warning into the prose, but it remains efficient and readable.

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?

Given the tool's moderate complexity (5 params, no annotations, output schema present), the description covers the essential context: what the tool does, the meaning of all parameters, a critical usage caveat, and a pointer to further documentation. It does not cover alternatives, but the output schema handles return structure, and the doc reference fills gaps. This is strong but not exhaustive.

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 provides only types and defaults, with 0% description coverage. The description compensates fully by explaining each parameter meaningfully: transform_id is 'fully qualified' and sourced from list_transforms, entity_type includes an example (maltego.Domain), entity_value is described as the 'value carried by the input entity,' settings are keyed, and timeout is in seconds. This adds substantial semantic value beyond the 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 starts with 'Run a transform against one input entity and return its results,' which clearly states the action (run), the resource (transform), and the scope (one input entity). This distinguishes it from sibling tools like list_transforms or get_transform, and the rest of the text reinforces the purpose.

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 provides a useful caution about checking entity count, which indirectly guides behavior when using the tool. However, it does not explicitly state when to choose run_transform over alternatives (e.g., get_transform or list_transforms), nor does it mention exclusions or preconditions. Usage context is implied but not fully articulated.

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