list_transforms

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

No annotations are provided, so the description carries the responsibility. It discloses a notable behavioral trait: an output type of NONE indicates a missing return annotation, which prevents Maltego client routing. This adds valuable context beyond a generic list and helps interpret results. Side effects aren't mentioned, but as a read-only listing operation, this is adequate.

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 two sentences: the first front-loads the main purpose, and the second adds a specific caveat about the NONE type. Both sentences are informative with no unnecessary words, making it highly concise and well structured.

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 simplicity (no params, output schema present), the description is complete. It states what is listed, includes the NONE-type explanation which aids output interpretation, and mentions the 'running server' context. No important details are 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?

The tool has zero parameters, so the baseline score of 4 applies. The description mentions input and output types, giving the user an expectation of what the tool reports without needing parameter definitions.

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 the tool lists every advertised transform with input and output types, using a specific verb ('list') and resource ('transforms'). It distinguishes from siblings like get_transform (single transform) and list_entities (different entity type), making the 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?

The description implies usage context: discovering available transforms on the running server. It doesn't explicitly name alternatives or state when not to use it, but the purpose is self-evident and the tool is simple enough that no further exclusions are needed.

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