Get Assembly status

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

With no annotations, the description bears full burden, but it only states 'Fetch' which implies a read operation. It does not disclose any behavioral traits such as idempotency, error handling (e.g., what if assembly not found), rate limiting, or whether it is safe to call repeatedly.

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 extremely short and front-loaded, but it sacrifices necessary detail. Every word is necessary, but it lacks completeness. Minimal viable length, but still adequate for a simple tool if supported by schema descriptions, which are absent.

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 presence of an output schema, the description need not explain return values. However, it fails to provide sufficient context for parameter usage and behavioral guidance. The tool is simple, but the description does not compensate for the lack of schema parameter descriptions or annotations.

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 description coverage is 0%, meaning the input schema provides no explanations for assembly_url or assembly_id. The description fails to clarify the difference between the two parameters, whether they are mutually exclusive, or how they are used. The agent cannot determine proper parameter usage from the description.

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 (Fetch) and the resource (Assembly status), distinguishing it from siblings like transloadit_create_assembly or transloadit_wait_for_assembly. However, it does not specify that the status is fetched by URL or ID, which is already implied by the input schema.

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?

No guidance on when to use this tool versus alternatives. For example, it does not differentiate from transloadit_wait_for_assembly, which also deals with assembly status. The agent is left to infer context from the name alone.

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