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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the 'privacy-filtered project metadata' qualifier, which hints at a behavioral trait (filtering), but it does not explain what the filtering entails, what the response contains, or whether the tool can fail (e.g., missing presentation). With annotations carrying the safety burden, a 3 is appropriate.

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 sentence with no wasted words, and the core action ('Read hosted get presentation') is front-loaded. It is concise, though it could be slightly more informative without becoming bloated.

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?

The tool has 5 parameters, no output schema, and no parameter documentation in the description. The description does not explain what 'privacy-filtered project metadata' means, what the return value is, or how the optional parameters (requestId, sessionId, executionId) affect the call. For a read tool with this many parameters, the description is under-specified.

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 0%, and the description does not explain any of the five parameters. The schema provides names and patterns, but the description does not clarify the roles of projectId, presentationId, requestId, sessionId, or executionId, nor which are required beyond the schema's required list. With zero coverage and no compensation in the description, the agent must guess parameter semantics.

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 ('Read') and resource ('hosted get presentation') and adds a qualifier ('using privacy-filtered project metadata'). It is clear enough to distinguish from siblings like list_presentations or get_presentation_authoring_brief, though it does not explicitly name an alternative.

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 implies a read operation for a hosted presentation, and the readOnlyHint annotation reinforces when it is appropriate. However, it does not explicitly state when to use this tool versus alternatives like presentation_read, get_presentation_authoring_brief, or list_presentations, nor does it mention any exclusions or prerequisites.

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