Update a prompt

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

The description is purely functional and adds no unique behavioral traits beyond the API endpoint structure. Since `readOnlyHint: false` is present, the description fails to add critical safety or side-effect context.

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 highly concise, consisting of only two short sentences that front-load the core function of the tool.

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?

While the schema is complete, the description itself is too brief for a mutation tool. A slightly more descriptive summary of what properties can be modified would improve agent instruction without redundant effort.

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?

Since schema description coverage is 100%, the baseline score of 3 is appropriate. The description adds no additional meaning or context to the specific input parameters like 'voice' or 'response_format' beyond their structure.

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 title and description clearly state the action (Update) and the resource (Prompt), making the function of the tool unambiguous.

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 provides no guidance on when to use this tool versus alternatives like creating or retrieving prompts. It relies solely on the agent knowing the distinct purpose of an 'update' operation.

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