ai_get_preview

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'get result' without stating whether it is a read-only operation, whether it can be called multiple times, or what happens if the task is still processing. This is a significant gap for an AI task retrieval tool.

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 compact, consisting of a one-sentence summary and a clear Args block. It is well-structured and avoids unnecessary detail, making it easy for an agent to parse.

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?

The description covers the tool's purpose and parameters, and an output schema exists, so return values are not needed. However, it does not address potential asynchronous behavior (e.g., task still running) or error scenarios, which are relevant for an AI task retrieval tool.

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?

With 0% schema description coverage, the description compensates by explaining all three parameters: project_uuid, schema_uuid, and task_uuid (specifically noting task_uuid comes from ai_preview_schema). This provides necessary meaning beyond the raw schema.

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 retrieves the result of an AI schema generation task using a specific verb ('Получить' = get) and a resource ('result of AI schema generation task'). It implies a retrieval operation, but does not explicitly distinguish it from the sibling tools ai_preview_schema and ai_apply_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?

The description provides a clear usage context by stating that task_uuid comes from ai_preview_schema, indicating the tool should be used after initiating an AI preview task. It does not mention explicit alternatives or exclusions, but the source of task_uuid gives enough guidance.

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