get_local_copy

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

With no annotations, the description carries the full burden and does well: it discloses the server-side export side effect, the creation of a temp .pptx, and revision-based cache invalidation ('re-exports only when the presentation has been saved since last export'). It omits where the temp file lives, whether it is overwritten/deleted, and any permission or failure behavior.

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?

Three short sentences, each earning its place: outcome first, then the local-vs-cloud branch, then the caching rule. Front-loaded and free of filler.

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?

For a single optional parameter with no output schema, the description covers the decision-relevant behavior (export, temp file, cache-by-revision). Minor gaps remain on the shape of the returned path/error cases, but nothing an agent needs to invoke it correctly is missing.

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% and the single presentationId is fully documented in-schema, including the 'optional when only one presentation is connected' nuance. The description adds no parameter-level meaning, so the baseline 3 applies.

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?

States a specific verb and resource: 'Returns a local file path for the presentation.' It further splits the two cases (already-local file vs. SharePoint/cloud export), so an agent knows exactly what artifact it gets. No sibling tool overlaps this purpose, so differentiation is implicitly clear.

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?

Usage is only implied: the reader infers this is the way to obtain a path for downstream file operations, and that cloud files incur an export. There is no explicit 'use this when' vs. 'use X instead', no prerequisites, and no guidance on when a fresh path is needed versus a cached one.

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