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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), but the description adds real context they don't: the five enumerated status values, the 0-to-1 progress scale, and the fact that per-target result and error details come back. It stops short of saying whether results can be polled repeatedly or how failures vs. partial states should be interpreted.

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 tightly packed sentence with the verb and identifier front-loaded and the return payload enumerated after the colon. Every clause carries information; there is no filler.

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 one-parameter read with no output schema, the description usefully enumerates the returned fields and the status vocabulary, which is the main thing an agent needs to interpret results. Minor gaps remain around polling behaviour and whether per-target arrays can be large, but nothing critical is missing.

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 a single parameter at 100% schema coverage, where the schema already explains the uuid format and that the value comes from create_publication. The description adds nothing about the id beyond restating 'by its id', so baseline 3 applies.

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 verb ('Check') and resource ('a publication by its id') and enumerates what is retrieved: status, progress, and per-target status/result/error. That is enough to separate it from create_publication and retry_publication, though it never explicitly names those siblings as alternatives.

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?

Usage is only implied: 'check ... by its id' suggests a read-after-create polling pattern, and the schema note that the id is 'The id create_publication returned' reinforces this, but the description itself gives no explicit when-to-use, polling cadence, or when to prefer retry_publication on failure.

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