Create a prompt

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

Annotations already declare this is a non-readonly, open-world, non-idempotent, non-destructive write operation. The description only repeats that it's a POST to /prompts, adding nothing about side effects, whether duplicate names overwrite, or what a 'prompt' represents in this system. No contradiction, but no value added.

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 short, so nothing is bloated, but the second clause '(POST /prompts)' just restates the HTTP verb already implied by the annotations and the tool name. It is appropriately sized but not information-dense.

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 6-parameter mutation tool with a required voice enum and no output schema, the description should explain what a prompt is, how voice/text/file relate, and what is returned. None of this is present, leaving significant gaps.

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%, so the baseline is 3. However the description contributes nothing about the meaning of name, voice, file, text, or description fields, and adds no clarification for the large voice enum beyond what the schema already lists.

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 is 'Create a prompt. (POST /prompts)' — it restates the tool name and title verbatim without adding any scope, target resource detail, or distinguishing behavior from siblings like placetel_update_prompt or placetel_list_prompts. There is no information an agent couldn't get from the name alone.

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?

No guidance on when to use this versus placetel_update_prompt, placetel_list_prompts, or placetel_get_prompt. It does not state prerequisites (e.g. required voice/name) or what happens when a prompt with the same name exists.

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