arsenkin_get_result

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

With no annotations, the description carries the full burden, but it does not disclose whether the call is read-only, whether it blocks until the result is ready, or what happens when the result is not yet available.

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?

A single sentence with no filler, but the awkward 'principal's' phrase and missing context reduce clarity.

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?

Even with an output schema present, the description omits the lifecycle context (when the result exists, whether to poll status first, and how this differs from export_result).

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 sole parameter job_id is not explained beyond the phrase 'Arsenkin job'; the description does not define where job_id comes from or how it relates to submit/batch_submit responses.

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 clear action ('Return') and resource ('durable result for the principal's Arsenkin job'), but leaves the meaning of 'principal's' and 'durable result' ambiguous, and does not distinguish itself from the sibling 'arsenkin_export_result'.

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 call this versus siblings like arsenkin_status, arsenkin_task_status, or arsenkin_export_result; no indication that it should be called after job completion or submission.

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