Check Website Edit Status

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

Describes the polling behavior, expected return fields (done, status, result), and termination conditions. Adds value beyond annotations which only indicate read-only and non-destructive nature.

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?

Two sentences with no filler, front-loading the purpose and providing actionable steps. Every sentence adds value.

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?

Given no output schema, the description explains the return contract (done, status, result) and polling logic. Missing details on error states or invalid workflow_id, but sufficient for the tool's simplicity.

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 coverage is 100% with a clear parameter description. The description reiterates the origin of workflow_id but does not add new semantic details beyond the schema.

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?

Clearly states the tool polls the status of a website-edit workflow, specifies the parent tool (edit_website), and distinguishes from sibling tools like check_website_status by referencing the workflow context.

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?

Explicitly tells when to call again (after poll_after_ms ms) and which parameter to pass (workflow_id from edit_website). Does not describe when not to use, but the context is clear for a polling tool.

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