get_generation

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

No annotations are provided, so the description carries the full burden. It usefully discloses the underlying endpoint and the semantics of the status values in the response, which is real behavioral context. It still omits what else a completed generation returns (e.g. asset URLs) and whether a missing uuid errors or returns empty.

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?

Three short, front-loaded fragments with no wasted words; the core action comes first. The status list is terse to the point of being slightly cryptic, with no delimiters or explanation of where those codes appear.

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?

There is no output schema, so the description is the only source for return semantics, and it covers only the status field. For a fetch-by-id tool, the agent should also know what a completed payload contains and how failures surface; that gap keeps it at minimum-viable.

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?

Single self-documenting parameter named 'uuid' at 0% schema description coverage. The phrase 'by uuid' confirms the identifier's role but adds nothing about format (e.g. that it must be a full UUID string) or error behavior for an unknown id.

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?

States a specific verb and resource: 'Fetch one generation by uuid', and 'one' implicitly contrasts with the sibling list_generations. It does not explicitly name an alternative, but the singular scope plus the lookup key makes 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?

No explicit when-to-use or when-not-to-use guidance, and the polling sibling wait_for_generation is never mentioned. However, the status code list ('1 processing, 2 completed, 3 failed') implies the intended use of checking whether a generation has finished, so usage is inferable rather than stated.

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