manus_website_publish

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

Discloses async nature and polling requirement, but lacks details on side effects, prerequisites, or permissions. No annotations to supplement, so moderate transparency.

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, no redundancy. Purpose and usage are front-loaded. Could be slightly improved with parameter hints, but still concise.

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?

Missing essential parameter semantics, no output schema, no error handling or return value description. Incomplete for a deployment tool with multiple optional parameters.

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?

All three parameters (task_id, visibility, website_id) have no descriptions in schema (0% coverage). Description provides zero explanation of parameters, leaving agent uncertain about usage.

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 action: 'Deploy the latest checkpoint of a website.' Distinguishes from sibling tools by specifying async behavior and naming 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?

Explicitly explains when to use this tool: async deployment requiring polling of status, or using sync alternative. Provides clear guidance on post-call actions.

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