Identify 10 common founder mistakes that break Dubai business setups. Filter by category to spot risks and avoid costly missteps before launching.
List 10 common founder mistakes that break Dubai setups.
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | Optional substring filter on the mistake title or id. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare this as read-only, idempotent, non-destructive, and closed-world. The description adds that the result is a fixed list of 10 mistakes focused on Dubai setups, but it does not add further behavioral context such as filtering behavior or source limitations.
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?
It is a single front-loaded sentence with no redundant or filler language. Every word contributes to the tool's purpose and scope.
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?
The tool is simple, has rich annotations, full parameter schema coverage, and an output schema, so the description is nearly complete for invocation. It could mention the optional category filter, but that detail is already handled by the schema.
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 100%, and the single optional category parameter is fully documented in the schema as a substring filter. The description adds no parameter-specific meaning beyond the schema, so the baseline of 3 applies.
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 uses a specific verb and resource: 'List 10 common founder mistakes that break Dubai setups.' It is clear what the tool returns, though it does not explicitly distinguish itself from adjacent advisory or planning tools such as setup_advisor or analyze_setup_decision.
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?
The description gives no guidance on when to use this tool versus alternatives, nor any exclusions. Usage is only implied by the topic, which is a gap in a large sibling toolset.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.