Check whether content has finished rendering before publishing. Returns the current rendering status so agents can confirm pages or posts are ready to review.
Check the current rendering status.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It omits what the status values are, whether it polls a queue, whether it needs a job identifier, and whether it's side-effect free. For a status-check tool with zero annotations that is a real gap.
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 short, front-loaded sentence with no filler. Appropriately sized for a zero-param status tool.
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?
Simple tool with an empty schema and no output schema, so the description needn't explain parameters or returns. But lacking annotations, it should at least hint at what is being reported on and any prerequisite, which it doesn't.
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?
Parameter count is 0, so baseline 4 applies. The description adds nothing param-related, but there is nothing to document.
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 ('Check') and resource ('rendering status'), so the purpose is clear. It doesn't differentiate from sibling 'render_video' (the trigger) or explain whether it reports on a specific render job, which leaves minor ambiguity.
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?
No guidance on when to call this versus waiting on 'render_video' or other status sources. With 50+ siblings, the agent gets no routing signal.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.