setup-zopio-app

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

With no annotations provided, the description carries the full burden of explaining behavior. It only says 'setup' and 'start components separately' but does not disclose what the setup actually does, whether it overwrites or creates resources, prerequisites, side effects, or whether it is long-running. This is a significant gap for a setup-type tool.

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?

The description is compact: a warning, a routing instruction, and a purpose statement. It is front-loaded and every sentence earns its place without unnecessary filler.

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?

For a single-parameter tool with a fully documented enum, the description provides enough to decide when to use it. However, because there are no annotations and no output schema, the lack of behavioral context about what setup entails and what consequences it may have leaves the description incomplete for safe invocation.

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?

The input schema fully documents the single appType parameter with an enum and descriptions, so the schema covers parameter semantics completely. The description adds no additional parameter-level detail, keeping this at the baseline of 3.

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 states a clear purpose: setting up specific Zopio components individually ('Zopio'nun belirli bileşenlerini ayrı ayrı başlatmak'). It also explicitly distinguishes itself from create-complete-application, which is the normal path, so an agent can tell them apart.

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 explicit usage conditions: 'Sadece özel durumlar için!' (only for special cases) and directly names the alternative for normal requests: 'Normal uygulama talepleri için create-complete-application kullan.' This leaves no ambiguity about when to select this tool.

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