create_app

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

With no annotations, the description discloses important traits: 'Non-destructive' and 'executes immediately', plus an authentication requirement. This adds useful context beyond the plain 'create' purpose, though it doesn't cover return values or error behavior.

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 brief and front-loaded, but the mention of 'prep_mode' (not in schema) and the conditional phrasing detracts from clarity. It's not as clean as it could be.

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 5-parameter create tool with no output schema, this description covers authentication and a usage condition but omits return values, error scenarios, and relationship to source code. It's adequate but incomplete.

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 coverage is 100%, so baseline is 3. The description adds a conditional note about 'prep_mode' which is not in the schema, potentially confusing agents. It doesn't meaningfully elaborate on the schema parameter descriptions.

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 the verb ('Creates') and resource ('new app') with a scope ('for the authenticated user'). It distinguishes from sibling tools like configure_app and publish_app by focusing on creation, though it doesn't explicitly name 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?

It provides authentication prerequisites and a conditional note about 'prep_mode', but does not explicitly say when to use this tool versus alternatives (e.g., configure_app). The guidance is implied rather than explicit.

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