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

Annotations already declare this as a non-read, non-destructive, idempotent operation. The description adds only 'hosted' and 'privacy-filtered project metadata,' but does not explain what that means operationally (e.g., queue creation, replacement behavior, side effects). It does not contradict annotations.

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 single sentence is brief, but its ambiguity ('Update...create...') means it does not serve as a clear, front-loaded statement. Conciseness without clarity is not a strength here.

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?

This is a complex tool with 12 parameters, a required idempotencyKey, an anyOf branch, nested objects, and no output schema. The description omits the two invocation modes (scoped creation vs replacement context), idempotency semantics, and expected behavior, leaving an agent unable to construct a correct call.

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?

With schema description coverage at 0%, the description must compensate, but it explains none of the 12 parameters. It mentions 'project metadata' abstractly without mapping to projectId, topic, description, idempotencyKey, replacementContext, or the meaning of the anyOf between scopeNodeId and replacementContext.

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 names a resource ('create presentation request') and a verb ('Update'), but the verb directly contradicts the tool name ('create'), leaving the core action ambiguous. It also does not distinguish this tool from sibling presentation-workflow tools such as publish_presentation_request or start_presentation_build.

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 is given on when to use this tool versus related siblings like retry_presentation_request, fail_presentation_request, or presentation_write. The description provides no context about the create-vs-replace modes implied by the anyOf schema or when each is appropriate.

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