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

Annotations already establish that the operation is read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds the privacy-filtering trait, which is useful behavioral context, but it does not disclose output shape, pagination, or what 'privacy-filtered' concretely excludes.

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 the verb and resource front-loaded and no filler. The wording 'hosted list presentations' is slightly awkward, but overall the definition is appropriately compact.

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?

A 5-parameter tool with no output schema and no parameter descriptions needs substantially more context. The description does not explain what is returned, how the required projectId is used, whether optional IDs filter the results, or how this relates to get_presentation in the sibling set.

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 names no parameters explicitly. The property names such as requestId, sessionId, executionId, and presentationId are self-descriptive, and 'project metadata' loosely hints at projectId, but the description adds no parameter-specific meaning to compensate for the empty schema descriptions.

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 action ('Read') and a resource ('hosted list presentations'), with the qualifier 'privacy-filtered project metadata' narrowing scope. However, the phrase 'hosted list presentations' is grammatically ambiguous and the description does not explicitly contrast with the sibling get_presentation, so it stops short of a 5.

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?

No guidance is given on when to use this tool versus close siblings such as get_presentation, get_pending_presentation_requests, or start_presentation_build. The 'privacy-filtered' phrase hints at a context but is not an explicit when-to-use or when-not-to-use condition.

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