createPrompt

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

No annotations are provided, so the description carries the full burden. It communicates that the tool creates a prompt (a mutation), but it does not disclose potential side effects such as overwriting an existing ID, validation rules, or required permissions. The curly braces rule is more about input formatting than behavioral side effects.

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 two sentences, front-loaded with the core purpose, and includes a constructive example. Every word earns its place; there is no fluff or repetition.

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 with two well-documented parameters, but it is a creation tool, and the description does not mention return values, error behavior, or idempotency. With no output schema and sibling tools, a bit more detail about what happens after creation would enhance completeness.

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%, with both id and contents thoroughly described, including the exact curly-braces rule and example. The description repeats these details without adding new meaning beyond the schema, so it stays 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 clearly states the action and resource: 'Create a new Teleprompter prompt.' This is a specific verb+resource pairing that immediately distinguishes it from sibling tools like usePrompt, searchPrompts, and listPrompts. The added example with curly braces further clarifies the tool's purpose.

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 implies usage for creating prompts via the verb 'create' and the template variable guidance, but it does not explicitly state when to use this tool over alternatives. No exclusions or alternative references are provided, leaving usage context to be inferred.

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