status

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 one real behavioral fact: results are freshly checked, never a stale PASS, which hints that invoking it may trigger re-evaluation rather than a cheap lookup. It says nothing about authorization, cost/latency of the check, whether the check has side effects, or what happens for an unknown batch_id.

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?

One compact sentence with the primary purpose front-loaded and no filler. It is terse to the point of leaving gaps, but no sentence 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 shape needn't be explained, and the freshness contract is covered. Still, for a tool with zero annotations and zero parameter documentation, the description leaves key operational facts (cost of a fresh check, failure mode for a bad batch_id, what 'metadata' includes) unstated.

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% and the only parameter, batch_id, is never mentioned in the description, so nothing is added beyond its self-explanatory name. The description should at minimum clarify the identifier format or expected source of the batch_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: returns batch metadata plus freshly computed status/counts for a batch. An agent can tell this is a read-and-report tool for a batch, though it does not distinguish itself from siblings like 'pending' or 'audit', which plausibly also report on batch state.

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?

'Never reuse an old PASS' implies the caller should invoke this to obtain a current verdict rather than trusting a cached one, which is a genuine usage signal. However, no explicit when-to-use/when-not-to-use framing or alternative (e.g., 'pending' for queue state, 'audit' for history) is named.

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