l2kc_reconcile_jobs

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

With no annotations, the description carries the full burden and does add real behavior: it never submits or resubmits ambiguous jobs, and mock data are test fixtures rather than a live account. It omits polling cadence, whether it blocks/waits, rate limits, and error behavior.

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?

Four short sentences, front-loaded with the verb phrase, and the test-fixture caveat is prominent. The ordering is slightly choppy (mock notice interrupts the operational semantics) but nothing is wasted.

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?

An output schema exists, so return values needn't be described, and the description covers the two things an agent needs to know: the wildcard behavior and the no-resubmit guarantee. Some gaps remain around polling/blocking behavior, but the definition is sufficient to invoke 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?

Schema description coverage is 0%, but the tool has only one optional parameter, so the description's explanation of the omit-``job_ids`` case covers the important semantic. It still doesn't clarify what happens when a specific list is passed (e.g., unknown or terminal IDs) or the expected ID format.

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 ('Poll job status'), and the reconcile semantics (never submits/resubmits ambiguous jobs) distinguish it from a plain status getter. It doesn't explicitly name gpu_get_job_status or l2kc_list_jobs, so the sibling boundary is only implied.

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?

Gives a concrete selection rule: omit ``job_ids`` to poll every active job, including ``UNKNOWN``. That tells the agent when this bulk mode applies, though it never explicitly contrasts with the singular get_job_status sibling.

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