add_presentation_text

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

No annotations are provided, so the description must carry the full behavioral burden. It only says 'Add a text box' and lists arguments; it does not disclose that the .pptx file is modified in place, that existing slide content is preserved, or what happens when the slide index is out of range. For a mutation tool, this is a meaningful transparency gap.

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 one-sentence purpose is front-loaded, followed by a compact, scannable Args list with one entry per parameter. There is no redundant or promotional text.

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?

Parameter definitions are complete enough to construct a valid call, and the purpose is clear. However, missing usage context, side-effect disclosure, and ordering relative to create_presentation/add_presentation_slide make it slightly incomplete for nuanced selection and error handling.

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 0% schema description coverage, the Args block compensates well: it gives units (inches, points), states that slide_index is 0-based, and enumerates alignment values ('left, center, right'). This adds the crucial semantic detail absent from the bare input schema.

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 first sentence states a specific action ('Add a text box') and resource ('a PowerPoint slide'), which clearly distinguishes this from sibling tools such as add_presentation_slide, create_presentation, and read_presentation. The named object leaves no ambiguity about what is being added.

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 use for inserting text into PowerPoint slides by mentioning path and slide index, but it never states when to prefer this over alternatives or mentions prerequisites like an existing presentation. There are no explicit exclusions or when-not-to-use conditions.

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