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

With no annotations provided, the description carries the burden of explaining behavior. It discloses the non-obvious polling protocol and references the response fields nextAction and pollAfterSeconds, which is exactly the behavioral context an agent needs. It does not cover auth, error behavior, or termination conditions, but the core polling semantics are transparent.

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 one compact sentence with the endpoint front-loaded followed by the conditional polling rule. No filler or repetition; every clause earns its place.

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?

For a simple one-parameter GET endpoint with an output schema, the description covers the essential call pattern and the polling logic. It doesn't enumerate return values (the output schema covers that) or discuss error handling, but nothing critical is missing for selecting and invoking the 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?

There is one required parameter, bulk_id, and the schema coverage in the description is 0%. The endpoint path embeds {bulk_id}, which gives a little context beyond the schema title 'Bulk Id', but the description never explains where the id comes from or what format it takes. For a single obvious parameter this is adequate, not enriched.

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 names a specific HTTP verb and resource (GET /v1/inference/pinned/bulk/{bulk_id}) and states the one-shot polling behavior, so an agent can see it performs a bulk-result fetch. However, it never names sibling tools such as hydracept_pinned_get or hydracept_pinned_run, so differentiation rests on the endpoint path rather than an explicit contrast.

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?

It gives a concrete usage instruction: call once, and if the response's nextAction is poll, wait pollAfterSeconds and call again. There is no guidance about when to choose this tool over the pinned_get/pinned_run siblings or when polling should stop, so the usage context is clear but incomplete.

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