List templates

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

With no annotations, the description should disclose behaviors like pagination, rate limits, or error handling, but it only mentions listing owned and builtin templates without further behavioral context.

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 very short and gets to the point quickly, but it could be more structured to include key information without excessive length.

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?

Despite having an output schema and 7 parameters, the description lacks explanation of pagination, sorting, filtering, and other critical details, making it incomplete for effective use.

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 coverage is 0%, leaving all 7 parameters undocumented. The description only briefly explains the 'include_builtin' parameter via a tip, failing to add meaning for other parameters like 'page', 'sort', or 'keywords'.

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 action 'List' and the resource 'Assembly Templates (owned and/or builtin)', distinguishing it from sibling tools that deal with assemblies, robots, or waiting.

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 specific tip for filtering built-in templates but does not give broader guidance on when to use this tool versus alternatives, such as transloadit_lint_assembly_instructions or transloadit_list_robots.

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