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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the same phm_ bearer token from submission is required, but says nothing about what a poll returns, job state transitions, whether polling is idempotent or rate-limited, or what happens if the job is unknown or still running — the core semantics of a polling tool.

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 tight sentence with the operation front-loaded and no filler. It is efficient, though it is arguably too compressed for the amount of behavior a polling endpoint needs to convey.

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?

No annotations, no output schema, and an undocumented parameter mean the description is the only channel for agent-relevant context, and it omits return shape, job-state interpretation, and retry behavior. For a polling tool this leaves an agent unable to interpret results confidently.

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 single job_id parameter has 0% schema description coverage and is not explained in the description either. The phrase 'previously submitted' hints that the id originates from submit_paid_machine_job, but the description adds no format, source, or validity detail beyond that implication.

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 (poll) and resource (a previously submitted autonomous machine job), which cleanly separates it from submit_paid_machine_job and quote_paid_machine_job in the sibling list. It stops short of naming those siblings explicitly, but the 'previously submitted' qualifier makes the lifecycle position unambiguous.

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?

'Poll a previously submitted' implies usage after submission, and the bearer-token clause is a real prerequisite. There is no explicit statement of when not to use it, no polling cadence or termination guidance, and no pointer to the submit/quote siblings as the counterpart operations.

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