MCP Hub

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

No annotations provided, so description carries full burden. It successfully communicates deprecation status (crucial behavioral context) but lacks disclosure of other behavioral traits like side effects, trigger mechanics, or what happens upon creation. Does not contradict annotations.

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?

Extremely concise and well-structured. Front-loaded with status tags ([UNIFIED] [DEPRECATED]), followed by purpose, then explicit alternative recommendation. No wasted words; every sentence earns its place.

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?

Adequate for a deprecated tool (primary goal is steering users to alternatives), but incomplete given 8 undocumented parameters and no output schema. Users forced to use this legacy tool would lack necessary parameter guidance, though the deprecation warning is prominent.

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 0% (8 parameters undocumented). Description fails to compensate by explaining critical parameters like 'actions' (what event actions?), 'collections' (which Directus collections?), or 'site' (identifier vs URL). Parameter names are partially self-explanatory but insufficient for complex arrays like 'actions' and 'collections'.

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 clearly states 'Create a new webhook' (specific verb + resource) and explicitly distinguishes from sibling tools by naming 'create_flow' and 'create_operation' as recommended alternatives. The [DEPRECATED] tag also clarifies current status.

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?

Excellent guidance provided: explicitly states when NOT to use ('Use Flows instead in Directus 10+') and names specific alternative tools ('see create_flow and create_operation'). This gives clear direction for tool selection.

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