GenOffice pptx patch (byte-preserving)

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

With no annotations provided, the description carries full burden — and it delivers richly. It discloses the byte-preserving behavior (only edited elements regenerated, untouched elements zip parts keep original bytes), the formatting template derivation from the first run/paragraph, the multi-line paragraph behavior, and the critical safety property of never modifying the original. This is exemplary disclosure for a patching tool.

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 description is dense but efficient — three sentences covering purpose, mechanism, formatting behavior, and safety. It front-loads the core action first. Slightly long for what it conveys but every sentence earns its place with distinct information.

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?

Given the tool has 4 params (100% schema coverage), no output schema (whose absence means no return-format obligation), and involves a nondestructive-but-mutating operation, the description is fully complete. It explains the patching mechanism, formatting constraints, multi-line handling, and output-path default behavior. No gaps that would mislead an agent.

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% (all 4 parameters documented in schema), so baseline is 3. The description adds context by explaining \n creates one paragraph per line and that the first run/paragraph is used as formatting template — connecting to the 'text' parameter's behavior. It adds modest value beyond the schema but the schema already does heavy lifting for path/outPath/slide descriptions.

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 clearly states 'Replace the text of one or more text elements on a slide of a .pptx' — a specific verb (replace) + resource (.pptx slide text elements). It distinguishes from siblings by naming 'GenOffice element-level byte-preserving patching' and explicitly contrasting with regenerate-all approaches. The scope (one slide, text-only) is precise.

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 explains the byte-preserving behavior, says it writes a NEW file and never modifies the original, and clarifies formatting template behavior (first run/paragraph) and how \n creates paragraphs. It doesn't explicitly name sibling alternatives (e.g., genoffice_pptx_create for new files, genoffice_pptx_delete for removals), but the context is sufficiently clear for when to use this tool vs creating/editing whole files.

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