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

The readOnlyHint and destructiveHint annotations already establish safety, and the description adds useful behavioral detail by naming the possible statuses (PENDING, RUNNING, COMPLETED, FAILED) and mentioning progress steps and error reporting. This goes beyond the annotation-only view without contradicting it.

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?

A single, focused sentence that front-loads the tool's core purpose and then lists the valuable return fields. There is no redundant or filler content.

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 single-parameter read-only status endpoint, the description is complete: it states what the tool checks, what it returns, and the schema plus annotations cover the remaining invocation requirements.

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 100%, and the jobId parameter is already well described as being returned by create_post, update_post, or publish_post. The main description adds no additional parameter semantics, so the baseline of 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 uses a specific verb ('Check') and resource ('status of a sync or publish job') and enumerates the exact return data (status, progress steps, error message). This clearly distinguishes get_job from sibling list_jobs, which would be for browsing jobs rather than checking a specific one.

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?

The description implies usage after starting a job, and the jobId schema description reinforces that the ID comes from create_post, update_post, or publish_post. However, there is no explicit guidance about when to prefer get_job over list_jobs or how it relates to polling workflows.

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