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

Adds substantial behavior beyond the annotations: asynchronous generation running 2-4 minutes in the background, immediate deal_id return, the required polling handoff to get_rebuild_status, and the guarantee that content and figures are preserved while numbers are checked against source. It also names the concrete outputs (shareable link, PDF, PowerPoint), which the annotation set does not convey.

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?

Purpose is front-loaded in the first clause, followed by input expectations and then the async mechanics, so the agent gets the 'what' before the 'how'. Every sentence carries distinct information; none restates the schema or the title.

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?

With no output schema, the description carries the return-value burden and does so: it states the call returns a deal_id immediately, how long generation takes, which tool retrieves the final link, and what artifacts come back. Nothing an agent needs to invoke or sequence this tool is absent.

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 the baseline is 3, but the description adds real operational meaning by telling the agent where the slide data comes from (PowerPoint, Google Slides or Keynote uploads) and that entries must be ordered title-then-body. The mode and instructions semantics are already carried by the schema, so this is a modest lift above baseline.

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 leads with a specific verb set (improve, redesign, polish, rebrand) applied to a clearly scoped resource: an existing presentation. The word 'existing' plus the slide-extraction instruction cleanly separates it from create_deck and create_sample_deck without needing to name them.

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 gives clear operative context: extract text from the user's uploaded deck, one entry per slide, and it explicitly routes the follow-up call to get_rebuild_status. What's missing is an explicit exclusion naming create_deck as the alternative when the user has no source deck, so the boundary is implied rather than stated.

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