local_ydb_pull_status

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

Provides detailed behavior beyond annotations: explains monotonic progress based on completed layers, the 0-99/100 range, and failure result (last observed value). This is valuable for caller expectations.

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?

Two clear sentences, action-first, with necessary detail. No fluff or redundancy.

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 no output schema, the description adequately explains the return semantics (progress value and meaning). It also covers failure behavior. This is sufficient for the caller to use the tool correctly.

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?

Only parameter jobId is described in schema as 'Background pull job id returned by local_ydb_pull_image.' The description reinforces this. Schema coverage is 100%, and description adds minor context, so a high but not perfect score.

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?

Clearly states the action: 'Check the status of a background Docker image pull' with a specific resource (pull job) and distinguishes from sibling like local_ydb_pull_image which initiates a pull.

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?

Implicitly indicates when to use (after a pull started by local_ydb_pull_image) but does not explicitly state that it should be polled repeatedly until complete. Could mention polling pattern or alternative status tools, but context is adequate.

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