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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious context beyond that: the null 'element' case for older or externally modified projects with script markup but no stored layout, which tells the agent not to treat null as an error.

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?

Two tight sentences, front-loaded with the action and identifier, with the edge case relegated to second position. No filler and nothing repeated from the annotations.

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?

Since an output schema exists, the description needn't document return structure, and it correctly stays brief while covering the one surprising return state (null element). The remaining gap is projectUid's role, which is left to the schema and is undocumented there too.

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 50% — slideUid is documented, projectUid is not. The description reinforces that slideUid is a *stable* identifier (as opposed to an index) and that it selects exactly one slide, but it says nothing about projectUid or how it scopes the lookup, leaving the uncovered half of the schema unaddressed.

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 ('Read one slide') and names the keying mechanism ('by its stable slideUid'), plus what comes back ('stored visual layout and on-screen text'). It's clearly distinct from get_project/get_document/update_slide, though it never explicitly contrasts itself with 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?

Usage is only implied — the read framing plus the 'stable slideUid' hint tells the agent this is the lookup path for a single known slide. There is no explicit when-to-use guidance, no mention of when to prefer get_document or a listing tool instead, and no stated prerequisites.

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