document.get_slide

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

No annotations are provided, so the description carries the full behavioral burden. 'Get' implies a read operation and the default-current behavior is useful, but the description does not disclose return shape, error behavior for out-of-range indexes, or whether an active document is required.

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 a single front-loaded sentence with no wasted words. The core operation and default behavior are communicated immediately.

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 simple single-parameter getter with no output schema, the description covers the basic invocation and default. It still leaves gaps around return values and index semantics, which are especially important given the absence of annotations and output schema.

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?

The schema has 0% description coverage for the single index parameter, so the description must compensate. It does explain that index selects a slide and that omitting it defaults to the current slide, but it does not clarify zero-based indexing or valid range despite the schema's minimum of 0.

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 states a specific verb and resource ('Get a single slide') and adds scope ('by index'), making the operation clear. It does not explicitly distinguish itself from siblings like document.list_slides or document.get_state, but the purpose is still readily identifiable.

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?

'default: current' gives useful guidance for when the index is omitted, implying the tool is used to fetch either a specified slide or the active one. However, it offers no explicit when-to-use guidance versus alternatives such as document.list_slides or document.get_state.

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