Server Quality Checklist

Tool Scores

• create_webhookC
  2.9/5.0
  Behavior2/5

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

  With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool registers a webhook and returns details, but lacks critical information such as authentication requirements, rate limits, whether the registration is persistent, or error handling. This is insufficient for a mutation tool with zero annotation coverage.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, efficient sentence that front-loads the key action and outcome with zero waste. It directly states what the tool does and the result, making it appropriately sized and well-structured.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool's complexity as a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits, error conditions, or what the returned 'webhook details' include, leaving significant gaps for an AI agent to understand and use the tool effectively.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The input schema has 100% description coverage, documenting both parameters ('url' and 'events') clearly. The description does not add any additional meaning or context beyond what the schema provides, such as examples or constraints, so it meets the baseline score of 3 for high schema coverage.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose4/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the tool's purpose: 'Register a new webhook to receive real-time notifications from Manus.' It specifies the verb ('register'), resource ('webhook'), and outcome ('receive real-time notifications'), but does not explicitly differentiate it from sibling tools like 'delete_webhook' beyond the action verb.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description provides no guidance on when to use this tool versus alternatives. It mentions the outcome but does not specify prerequisites, context, or exclusions, such as when to choose this over other notification methods or how it relates to sibling tools like 'create_task'.

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

• delete_webhookC
  2.9/5.0
  Behavior2/5

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

  With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a removal/deletion operation, implying it's destructive, but doesn't clarify whether deletion is permanent, reversible, or has side effects. No information about permissions, rate limits, or response format is included, leaving significant gaps for a mutation tool.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, efficient sentence that communicates the core purpose without unnecessary words. It's appropriately sized for a simple deletion tool and front-loads the essential information. Every word earns its place with no redundancy or fluff.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a destructive operation with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after deletion, whether confirmation is required, or what the response contains. Given the tool's potential impact and lack of structured metadata, more behavioral context is needed to make it complete for safe agent use.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 100%, so the parameter 'webhook_id' is fully documented in the schema. The description adds no additional semantic context about the parameter beyond what the schema provides ('The ID of the webhook to delete'). This meets the baseline expectation when schema coverage is complete.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose4/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the action ('Remove') and target ('previously registered webhook by its ID'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'create_webhook', but the verb 'Remove' versus 'create' provides implicit distinction. The description avoids tautology by specifying what gets removed rather than just restating the tool name.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description provides no guidance on when to use this tool versus alternatives or what prerequisites exist. While 'previously registered' implies the webhook must exist, it doesn't specify conditions for deletion or warn about consequences. There's no mention of sibling tools like 'create_webhook' for comparison or when deletion might be appropriate versus modification.

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

• create_taskB
  3.1/5.0
  Behavior2/5

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

  With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that it 'Returns task_id, task_title, task_url, and optionally a shareable link,' which gives some output context, but lacks details on permissions, rate limits, side effects, or error handling for a creation tool.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, efficient sentence that front-loads the core action and key return values, with no wasted words. It effectively communicates the essential information in a compact form.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the complexity of a creation tool with 6 parameters and no annotations or output schema, the description is minimally adequate. It covers the basic purpose and return values but lacks behavioral context and usage guidelines, leaving gaps for an AI agent to infer details.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The input schema has 100% description coverage, so the schema fully documents all 6 parameters. The description adds no additional meaning beyond the schema, such as explaining interactions between parameters or usage examples, meeting the baseline for high schema coverage.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose4/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the action ('Create a new AI task in Manus') and specifies the resource ('AI task'), which is distinct from sibling tools like create_webhook and delete_webhook. However, it doesn't explicitly differentiate from siblings beyond the resource type, missing a direct comparison.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description provides no guidance on when to use this tool versus alternatives, such as when to create a task versus a webhook, or any prerequisites like authentication needs. It only mentions the return values without context for usage decisions.

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