Get Assembly status

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

No annotations are provided, and the description only says 'fetch' without detailing behavioral traits like idempotency, authentication requirements, or error behavior. The description is too minimal to compensate for the lack of annotations.

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 concise sentence that directly answers what the tool does. No unnecessary words, perfectly sized for a simple fetch operation.

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 and the existence of an output schema, the description does not need to explain return values. However, it lacks information about error scenarios or relationship to sibling tools, which would help in a broader context.

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 description adds the context that the parameters are for identifying the assembly by 'URL or ID', which is not present in the schema (which only has string types). However, it does not specify format, precedence, or exclusivity, so it provides minimal additional meaning.

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 it fetches the latest Assembly status, which is a specific verb-resource combination. This distinguishes it from sibling tools like transloadit_create_assembly (creation) and transloadit_wait_for_assembly (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 does not provide guidance on when to use this tool vs alternatives. It only mentions the parameters (URL or ID) but no contextual instructions, such as preferring this over transloadit_wait_for_assembly for a one-time check.

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