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

Annotations already supply readOnlyHint and openWorldHint, and the description adds useful context beyond them: 'Allowlisted, unbilled' (no auth, no cost) and ETA-based polling behavior. These are genuine behavioral disclosures, though the phrasing 'scraping preview' and 'discovery reports blueprint maintenance' is garbled and adds noise rather than clarity.

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 core purpose is front-loaded in the first sentence, which is good. The second sentence is a confusing semicolon-joined bundle of jargon ('Allowlisted, unbilled scraping preview; discovery reports blueprint maintenance') that obscures rather than informs.

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?

With no output schema and a single undocumented parameter, the description carries real burden. It partially covers the tool's nature (read-only metadata), cost/auth status, and polling cadence, but omits what metadata is returned, the meaning of the ETA, and failure behavior.

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 (job_id as a uuid) and schema description coverage is 0%, so the schema documents nothing about it. The description never mentions job_id, its format, or how to obtain it, leaving a coverage gap it should have compensated for.

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 first sentence gives a clear verb+resource+scope: 'Read Job metadata only,' which distinguishes it from the sibling get_results by explicitly limiting the return to metadata. However, the remaining fragments ('discovery reports blueprint maintenance') are cryptic domain jargon and don't sharpen the purpose further.

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?

'Follow the ETA before polling again' gives an actionable polling cadence, implying this is a poll-until-complete tool. But it never names alternatives (get_results, submit_job) or when NOT to use it, so the guidance is implied rather than explicit.

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