get_page

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

No annotations are provided, so the description carries the burden. It states the return format (string with details including elements and layout) but does not disclose other behavioral traits like read-only nature, error behavior, or performance implications.

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 structured with an Args section, making it easy to parse. It is concise with no redundant information, though the Args format adds slight verbosity.

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's simplicity (3 required params, no enums, no nested objects) and the presence of an output schema in the context, the description adequately covers the tool's purpose, parameters, and return value. Missing are error conditions or edge cases, but it is complete for basic use.

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 input schema has 0% description coverage, but the tool's description explicitly lists and describes each of the three parameters (user_google_email, presentation_id, page_object_id) with their types, adding meaning beyond the schema's unlabeled properties.

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 'Get details about a specific page (slide) in a presentation' with a specific verb and resource. It distinguishes from siblings like 'get_presentation' (entire presentation) and 'get_page_thumbnail' (thumbnail image).

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 does not provide explicit guidance on when to use this tool versus alternatives or prerequisites. The purpose is implicit, but no exclusions or conditions are mentioned.

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