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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered structurally. The description adds one useful behavioral detail — output is privacy-filtered project metadata — but says nothing about permissions, error behavior, or filtering rules.

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?

It is a single short sentence with the verb front-loaded, so there is no padding. However, the awkward construction "Read hosted get presentation" hurts readability rather than adding value.

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?

With 5 parameters, no output schema, and a read operation over hosted presentations, the description should say at minimum what is returned and how it differs from sibling read tools. Neither is present, leaving the definition inadequate for correct invocation.

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 description coverage is 100%, so the baseline is 3, and the description contributes no additional parameter meaning. Notably the schema descriptions are copy-pasted boilerplate (every field, including presentationId, is described as a project ID), which the description does nothing to clarify.

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 phrase "Read hosted get presentation" is a garbled restatement of the tool name, though "privacy-filtered project metadata" hints at retrieval scope. It does not distinguish this tool from close siblings like presentation_read, list_presentations, or get_presentation_authoring_brief, so an agent cannot tell which read path to take.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative, which is a real gap given several sibling read tools (presentation_read, list_presentations). The agent is left to infer selection from the name alone.

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